Hi Willy, On 01/12/2011 01:55 AM, Willy Lambert wrote: > Hi all, > > for memory I have been trying to makes socketCan working on my Ixxat board > for some time. It is stacked on a PC104 cpu module with a linux debian > squeeze. After having a fully hardware configuration (a proper node + can > analyser) I tried Ixxat drivers and succeed after soldering a jumper on the > board and setting some BIOS values. After this I quickly tested a socketCan > version from svn and it seems to works (at least interrupts were triggered). > > Cleaning time arrived and I complety reinstall the linux with only the > required kernel configuration. The choosed kernel is a 2.6.35.7. > My first question is : may I use kernel official sources of socketCan ? or > do I need to checkout something ? > > I activated theses options : > >> [*] Networking Support --> >> --- [*] CAN bus subsystem support --> >> ----------[*] Raw Can Protocol (raw access with CAN-ID filtering) >> ----------[*] Broadcast Manager CAN Protocol (with content filtering) >> ---------- CAN Device Drivers ---> >> ----------------- [*] Virtual Local CAN Interface (vcan) >> ----------------- [*] Platform CAN drivers with Netlonk support >> ----------------- [*] CAN bit-timing calculation >> ----------------- [*] Philips/NXP SJA1000 devices --> >> -------------------------[M] ISA Bus based legacy SJA1000 driver >> > All remark is welcome (espacially if I need to choose "M" instead of "*") > > I setup my can0 interface in the rc.local script : > >> modprobe sja1000_isa irq=3 mem=0XD0000
Why do you use irq=3 now. IIRC, it's used for the serial port. Why not irq=5? Wolfgang. _______________________________________________ Socketcan-users mailing list [email protected] https://lists.berlios.de/mailman/listinfo/socketcan-users
