On Sunday 21 March 2010, christian pellegrin wrote: > > Anybody know the right thing to do here?
when to register consoles is a general mess. I've seeen some success in having it be board-specific data, at the level of "port 3 should be a console ... or in this case, maybe having platform data say which chip. After all, board docs probably assign numbers to each of the external connetors, and say "#1 is normally the onsole" (or maybe #0, #3, etc). But it's still kind of chaotic trying to set things up so that for example $3 becomes /dev/ttyS3" and so forth. Especially if your chip has six serial ports but several of them aren't wired up (and so should not get published to userspace even if they do get autodetected... (Heck, the controller may exist, but the unavailability may as easily be "those pins are routed to some other peripheral" as ""those pins aren't wired up to RS232 level shifters or a DB9/RJ45/... connector. . ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ spi-devel-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/spi-devel-general
