Just discovered that this morning! Had made the assumption it was automatically enabled, but only clued onto it when I noticed udevmonitor wasn't giving only UEVENT output, not UDEV output. Should have been obvious, but I kept barking up the wrong tree!

So, turning out to be a good chance to learn how the lower levels of a linux system work and managed to learn exactly how udev works while stumbling on this one.
Thanks for the reply

2008/4/21 Detlev Zundel <dzu@denx.de>:
Hi Daniel,

> I'm currently trying to compile a kernel for an AMCC440EP board within an eldk
> environment. We've got a FTDI usb2serial converter we need to connect to the
> board. Now I've compiled a kernel on a gentoo machine for this device and had
> no problems. With this board, the kernel recognizes the device fine:
>
> ftdi_sio 1-1:1.0: FTDI USB Serial Device converter detected
> usb 1-1: FTDI USB Serial Device converter now attached to ttyUSB0
> drivers/usb/serial/ftdi_sio.c: v1.4.3:USB FTDI Serial Converters Driver
>
> but udev doesn't actually make the ttyUSB0 node. If anyone knows what may have
> caused the problem and how to fix it, it'd be much appreciated.

Maybe udev isn't running at all?  The ELDKs including udev disable it
per default (what version are you using?).  Embedded systeme like to
have static kernel configurations presenting no surprises at runtime...

Cheers
 Detlev

--
Programming X-Windows is like trying to find the square root of pi
using roman numerals.
                                         -- The UNIX Haters Handbook
--
DENX Software Engineering GmbH,      MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich,  Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-40 Fax: (+49)-8142-66989-80 Email: dzu@denx.de

_______________________________________________
Linuxppc-embedded mailing list
Linuxppc-embedded@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded