| 1 |
Graham Murray posted on Sat, 14 Jul 2012 07:13:56 +0100 as excerpted: |
| 2 |
|
| 3 |
> "Walter Dnes" <waltdnes@××××××××.org> writes: |
| 4 |
> |
| 5 |
>> Do you realize this would effectively kill linux in the embedded |
| 6 |
>> device area? Udev, even without the systemd code, is simply to large |
| 7 |
>> for embedded devices. |
| 8 |
> |
| 9 |
> But surely most embedded devices do not need hotplug functionality, they |
| 10 |
> have a known, fixed, set of devices. So should static nodes in /dev/ not |
| 11 |
> be sufficient? |
| 12 |
|
| 13 |
Well, there's (kernel-side) devfs as well, as others have mentioned. |
| 14 |
|
| 15 |
Meanwhile, "embedded" can mean different things to different users of the |
| 16 |
term. I expect few would argue that onboard boot devices on embedded are |
| 17 |
likely to change, but there's a lot of (arguably embedded) devices with |
| 18 |
USB-host support these days, and some form of dynamic device-nodes, even |
| 19 |
if it's just devfs, can make that much more flexible and easier to deal |
| 20 |
with. |
| 21 |
|
| 22 |
What's interesting is the potential on such devices for USB-based |
| 23 |
storage, displays, sound, net and HID, blurring the definition of |
| 24 |
"embedded" even further, altho one would hope nobody tries to connect all |
| 25 |
of those up to the same host USB port (via hub) at the same time as I can |
| 26 |
just imagine the bandwidth management headaches trying to do so, thus |
| 27 |
implying 2-3 USB host-ports, minimum. |
| 28 |
|
| 29 |
-- |
| 30 |
Duncan - List replies preferred. No HTML msgs. |
| 31 |
"Every nonfree program has a lord, a master -- |
| 32 |
and if you use the program, he is your master." Richard Stallman |
Archives