On Thu, Nov 5, 2009 at 6:16 PM, Paul Thomas <[email protected]> wrote: > Hello, > > I've been trying out Christian's new patch for net-next-2.6. I got it > to compile, and it even successfully probes the device on startup. I > get a can0 entry in /proc/net/dev. When I do "ip -details link show > can0" I get: > 2: can0: <NOARP,40000> mtu 16 qdisc noop state DOWN qlen 10 > link/[280] > can > > This looks OK, but when I do "ifconfig can0 up" I get "SIOCSIFFLAGS: > Invalid argument". This is an arm system using an embedian filesystem. > > Any thoughts? > > thanks, > Paul >
OK, I think I know some of the problem. First when I look at the debug output after running the ifconfig up I get useful output: mcp251x spi1.3: MCP251x didn't wake-up mcp251x spi1.3: bit-timing not yet defined mcp251x spi1.3: unable to set initial baudrate! When I see this message I don't get any activity on DO, but during startup there is activity on DO during the probe. So it looks like it's just not coming out of sleep. On this board the only connections to the host processor are the 4 SPI pins and INT (pin 12 on 18 pin version), but the irq pin (INT) isn't even defined. Do I need some other connection for the driver? Tomorrow I'll try and not put the part to sleep and see if that works. thanks, Paul _______________________________________________ Socketcan-core mailing list [email protected] https://lists.berlios.de/mailman/listinfo/socketcan-core
