PCI resource collision message

Hi all, I have seen the following message in /var/log/messages file :- PCI: Device :01:00.0 not available because of resource collisions Whenever this msg comes, the PCI card which is present in :01:00.0 is not useful/accessible. While detection of card, pci_set_master() fails. But after

IRQ handler receive BAD struct pt_regs

hi, These days i wrote a interrupt handler program, i wanted get CPU context when the interrupt came.But in my handler, i get the wrong "struct *pt_regs",this was kernel delivering to me,and the IRQ number and "void* data" was right. who can give me some advice about this mistake? Sincerely yours

Re: module state:permanent

Thanks Sandeep, but still the question holds. Why this module would become permanent ? ~amit On Wed, Dec 10, 2008 at 11:46 AM, Sandeep K Sinha <[EMAIL PROTECTED]>wrote: > Ya that's right. > > On Wed, Dec 10, 2008 at 10:48 AM, amit mehta <[EMAIL PROTECTED]> wrote: > > Hi All, > > > > Why would so

Re: module state:permanent

Ya that's right. On Wed, Dec 10, 2008 at 10:48 AM, amit mehta <[EMAIL PROTECTED]> wrote: > Hi All, > > Why would some module's state become permanent ? > i inserted one module and when i try to remove it, i get: > ERROR: Removing 'procsfs1': Device or resource busy > > > > Module

module state:permanent

Hi All, Why would some module's state become permanent ? i inserted one module and when i try to remove it, i get: *ERROR: Removing 'procsfs1': Device or resource busy* Module Size Used by procsfs13204 0 [permanent] <- The program code is here: http

Re: USB Gadget Drivers

Here is the home page of Linux USB Mass storage driver: http://www2.one-eyed-alien.net/~mdharm/linux-usb/ USB Mass storage class is very well supported in Linux kernel. You have to write code specific to your USB controller only. The code for USB protocol and mass-storage class is already there.