Kurt Van Dijck wrote: > On Sat, Oct 03, 2009 at 02:33:27PM +0200, Oliver Hartkopp wrote: >> Kurt Van Dijck wrote: > [...] >> So it's not only 'enabling' and 'disabling' the transceiver, there is need to >> control and read the transceiver states and get some properties like >> max_phy_bitrate or something like this. >> >> Does you approach allow these more complex dependencies also? >> Or is probably the PHY abstraction layer >> >> linux/Documentation/networking/phy.txt >> >> something, we should take a look at? >> >> As i'm not a 'platform' specialist maybe someone (like you) could give some >> feedback to these requirements. > I started working on a patch series, that adds a CAN transceiver class > that could be a basis for such extended functionality. > When ready (few days maybe), I'll resume this.
Thanks. If you're interested, i can provide some block schematics that explain how fault tolerant transceivers are wired in power-on-CAN setups that are used in automotive environments. I'm looking forward to your ideas! Regards, Oliver _______________________________________________ Socketcan-core mailing list [email protected] https://lists.berlios.de/mailman/listinfo/socketcan-core
