| 00:20.21 | *** join/#elinux infobot (ibot@208.53.50.136) |
| 00:20.21 | *** topic/#elinux is http://eLinux.org/ || Ask anything; it may take 24+ hours to get a response. Mailing lists -> http://elinux.org/ELinuxWiki:Mailing_List ; Logs available at ibot.rikers.org |
| 00:20.21 | *** mode/#elinux [+o infobot] by ChanServ |
| 00:37.55 | ildar[m] | https://elinux.org/Embedded_Linux_Distributions is waaay outdated. Anyone have a link to overview of current platforms? Especially dev powers and updates share? |
| 00:46.56 | *** join/#elinux learningc (~User@mti-37-145.tm.net.my) |
| 03:39.41 | Guest40467 | ildar[m]: feel free to update that page as you learn more |
| 03:40.20 | *** mode/#elinux [+o wmat] by ChanServ |
| 04:31.00 | *** join/#elinux User__ (~User@mti-37-145.tm.net.my) |
| 05:00.28 | *** join/#elinux vstehle (~vstehle@rqp06-1-88-178-86-202.fbx.proxad.net) |
| 05:09.33 | *** join/#elinux vorpalblade77 (~vorpalbla@98.127.110.44) |
| 05:14.11 | *** join/#elinux vorpalblade77 (~vorpalbla@98.127.110.44) |
| 05:39.13 | *** join/#elinux learningc (~User@mti-37-145.tm.net.my) |
| 06:10.29 | *** join/#elinux lyakh (~lyakh@cable-87-78-226-14.netcologne.de) |
| 06:19.26 | *** join/#elinux t0mmy (~tprrt@ram31-1-82-234-79-177.fbx.proxad.net) |
| 07:08.45 | *** join/#elinux diego_r (~diego@host57-224-static.7-79-b.business.telecomitalia.it) |
| 07:10.11 | *** join/#elinux Bunio_FH (~bunio@81-18-201-214.static.chello.pl) |
| 09:46.22 | *** join/#elinux quarterback (~quarterba@unaffiliated/quarterback) |
| 09:58.46 | quarterback | A general question about embedded linux. If an embedded linux os is to be setup on a 32 bit board with arm or ppc processor. How many engineers would be needed to setup up the software platfom? I am thinking of peripherals such as gps, audio, video or communication etc. |
| 09:59.47 | quarterback | Looking at embedded linux, it seems rather complex to be done from scratch. I take that I have to start with an existing baseline of some board and modify/tweak it to suit my hardware.. |
| 10:03.03 | *** join/#elinux jkridner (~jkridner@pdpc/supporter/active/jkridner) |
| 10:10.38 | ildar[m] | The important question here is: is BSP available and how complete it is? |
| 10:12.00 | quarterback | ildar[m], BSP is available for the platform but not for peripherals. So software for peripherals may have to be developed from scratch or from peripherals of other hardware. |
| 10:14.11 | ildar[m] | sent a long message: < https://matrix.org/_matrix/media/v1/download/matrix.org/mMBaHSpGUcXQHUJzeKznSeTy > |
| 10:15.44 | ildar[m] | so how complete BSP is? Some BSPs have e.g. Linux kernel already. |
| 10:17.40 | quarterback | ildar[m], I am thinking that the board would be similar to raspberry pi, with a ready linux kernel for it. |
| 10:19.44 | ildar[m] | then the kernel version maybe quite important: some eLinux platforms have minimal kernel version requirement. |
| 10:21.29 | quarterback | ildar[m], How is it possible to enable peripherals on the board? Do majot elinux platforms have drivers for popular peripherals on a processor? I recall that I had seen about 150 people who worked on a smart phone platform that had embedded linux in it. |
| 10:21.36 | quarterback | major* |
| 10:50.26 | rohieb|ptx | wonders what "major elinux platforms" are |
| 10:51.38 | rohieb|ptx | quarterback: I think you cannot compare smartphones to general embedded linux devices, as the ecosystem for android is different in some key points |
| 10:52.48 | quarterback | rohieb|ptx, Yes, I agree |
| 10:52.55 | rohieb|ptx | but if you stick to an ARM platform that has upstream kernel support, and linux drivers are available, you will get less problems than if no drivers or no linux support is available |
| 10:53.43 | quarterback | rohieb|ptx, Yes, arm seems to have upstream kernel support for most of its processors. |
| 10:54.44 | rohieb|ptx | the zone between that can be very flexible in terms of how many work needs to be done. even with all support in upstream linux it can happen to you that due some customer requirement you will need to patch the kernel in orders of 100-200 patches |
| 10:55.50 | rohieb|ptx | and talking about the general platform support, not only kernel land but user land too, is probably even another ballpark |
| 10:55.56 | quarterback | That would mean lot of effort I suppose. |
| 10:56.33 | quarterback | userland is huge. I am talking about boards without a screen. Just some blinking lights and a gps or other communication modules. |
| 10:56.39 | rohieb|ptx | yes, it doesn't have to, but it could be. you have to know your requirements. |
| 10:56.57 | rohieb|ptx | yeah, but someone wants to use that GPS, no? that will be a userland application :-) |
| 10:58.20 | quarterback | I am used to working with scopes and physical signals like voltages, currents. The thing about embedded linux is that everything is on terminal and with peripherals like jtag or usb. This is a big change for me. |
| 11:10.40 | ildar[m] | well, this vastly depends on particular peripherals models. |
| 11:10.53 | ildar[m] | some have drivers mainlined (in vanilla Linux sources) |
| 11:11.11 | *** join/#elinux t0mmy (~tprrt@ram31-1-82-234-79-177.fbx.proxad.net) |
| 11:11.19 | ildar[m] | most are added by patches. |
| 11:11.31 | quarterback | Some seem to have drivers but most of them were developed like 4~5 years ago. |
| 11:11.58 | ildar[m] | but noone can tell about thingies you didn't name yet ))) |
| 11:12.42 | quarterback | The companies which have embedded linux in them seem to have developed many of the drivers on their own. |
| 11:17.23 | ildar[m] | e.g. SPI-connected devices in vanilla Linux: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/spi/Kconfig |
| 11:18.10 | quarterback | I can do this perhaps. |
| 11:20.32 | quarterback | How do people get boards so that they develop drivers for them? |
| 11:23.33 | ildar[m] | emm, wrong. That's just core&controllers. Devices are spread in drivers/ tree |
| 11:26.55 | ildar[m] | e.g. CONFIG_NFC_NCI_SPI , CONFIG_AD525X_DPOT_SPI , CONFIG_JOYSTICK_PSXPAD_SPI , CONFIG_TOUCHSCREEN_AD7879_SPI |
| 11:26.58 | ildar[m] | etc,etc |
| 11:27.07 | quarterback | Are you a author of above? |
| 11:28.00 | *** join/#elinux jkridner (~jkridner@pdpc/supporter/active/jkridner) |
| 11:42.53 | quarterback | ildar[m], Thanks for your suggestions. |
| 12:11.32 | *** join/#elinux t0mmy (~tprrt@217.114.201.133) |
| 13:22.45 | *** join/#elinux dc13ff (uid190567@gateway/web/irccloud.com/x-qsxuvmqqzcoarnof) |
| 13:55.59 | *** join/#elinux rcw (~rcw@128.224.252.2) |
| 14:29.22 | *** join/#elinux quarterback (~quarterba@unaffiliated/quarterback) |
| 14:34.19 | *** join/#elinux vorpalblade77 (~vorpalbla@98.127.110.44) |
| 14:39.03 | *** join/#elinux vorpalblade77 (~vorpalbla@98.127.110.44) |
| 17:38.30 | *** join/#elinux dc13ff (uid190567@gateway/web/irccloud.com/x-zohvgwyosadipbpy) |
| 18:38.06 | *** join/#elinux nemunaire (~nemunaire@2a01:e35:8bb7:3c60::2) |
| 19:07.03 | *** join/#elinux t0mmy (~tprrt@ram31-1-82-234-79-177.fbx.proxad.net) |
| 19:12.19 | *** join/#elinux shoragan (~shoragan@debian/developer/shoragan) |
| 19:25.50 | *** join/#elinux diego_r (~diego@2.43.161.138) |