Don't kill me but a collegue has bump me into something : I did compile linux kernel socket can sources... I must be trying something that is outdated ...
2010/11/29 Willy Lambert <[email protected]> > I found in the code that the driver supports another option than the one > tha was suggested by Ixxat to me for module loading : > type=04ISA instead of old use of type=03ISA, I don't really know if it > change something else than printed messages but you have to know I changed > this (and waiting for an Ixxat confirmation of this). > > Here is the piece of code doing ioremap (hope I won't broke a license, it's > quite minimal) : > >> Dev->DPRAM.VirtAddr = >> (unsigned long) ioremap (Dev->DPRAM.PhysAddr, Dev->DPRAM.Size); >> >> PRINTD ("DPRAM requested at 0x%lx size %d and remapped to 0x%lx\n", >> Dev->DPRAM.PhysAddr, Dev->DPRAM.Size, Dev->DPRAM.VirtAddr); >> > > I activated Debug messages in dmesg so I have : > [ 2871.507705] KDEB: DPRAM requested at 0xd0000 size 4096 and remapped to > 0xc00d0000 > > [ 2871.480450] can: controller area network core (rev 20090105 abi 8) > [ 2871.480525] NET: Registered protocol family 29 > [ 2871.487568] can: raw protocol (rev 20090105) > [ 2871.496096] can: broadcast manager protocol (rev 20090105 t) > [ 2871.502655] sja1000 CAN netdevice driver > [ 2871.507657] KINF: CAN PC-I driver v4.1b for BCI v4.5.8 Compiled Nov 29 > 2010 at 22:46:27 > [ 2871.507690] KDEB: Device : type [04ISA], addr 0xd000 > [ 2871.507696] KDEB: Device name is [PCI-I04 ISA Passive PC/CAN Interface] > [ 2871.507705] KDEB: DPRAM requested at 0xd0000 size 4096 and remapped to > 0xc00d0000 > [ 2871.507795] KDEB: Port 0 found. Ptr 0xc00d0000 with ret 0 > [ 2871.507799] KDEB: Release port 0 > [ 2871.507887] KDEB: Port 1 found. Ptr 0xc00d0200 with ret 0 > [ 2871.507891] KDEB: Release port 1 > [ 2871.507899] KINF: Device registered successfully for 2 ports. Major > [250] > [ 2871.507905] KDEB: Allocate > [ 2871.508131] KDEB: Free > [ 2871.508164] KINF: IRQ number [5] registered > [ 2871.508170] KDEB: Allocate > [ 2871.508370] KDEB: Free > [ 2871.508381] KINF: IRQ will be not registered for port 1 > > > > 2010/11/29 Wolfgang Grandegger <[email protected]> > >> On 11/29/2010 10:00 PM, Willy Lambert wrote: >> >> > My docs says : >> > _ basis adress (0xD0000 for me) + 0x0000 to 0x00FF : CAN-Controller 1 >> > _ basis adress + 0x0100 to 0x01FF : Reset CAN1 >> > _ basis adress + 0x0200 to 0x02FF : CAN-Controller 2 >> > _ basis adress + 0x0300 to 0x03FF : Reset CAN2 >> > So I there is still a stange difference between one controller range and >> the >> > 0x20 byte register of SJA1000. Maybe the only problem interfacing my >> board >> > with socket can is here... >> >> Well, it just says that the Reset-Region starts at offset 0x200. Does >> the IXXAT driver touch that region? If yes, where? And how are the >> registers accessed? >> >> > They told me explicitly to use only one IRQ for both controllers : >> > >> >> me > I can't write irq=5,7 as stated in the docs >> >> ixxat > Please use the same IRQ for both CAN controllers. >> >> OK, then irq=5,5 should just work fine. >> >> > But anyway, at the moment making just one working is enougth. I will >> setup >> > the second one when I'll have something working. >> > >> > I'll do my best to instrument this code and give you the result >> >> Good luck. >> >> Wolfgang. >> > >
_______________________________________________ Socketcan-users mailing list [email protected] https://lists.berlios.de/mailman/listinfo/socketcan-users
