Re: sysfs entries for the character driver

ainline submission i think this won't be a problem. And all the hardware specific details will be exposed through the pci_dev structure. Arun C

Re: Loading modules on every boot

o create nodes automatically. somebody please correct me if I am wrong Arun C

Re: Loading modules on every boot

which is not yet controlled by any driver it will load your > module. > > The other way is to use the init script which is being executed on system > boot. > This is for automatic insertion of the module. But for automatic device node creation 'udev' is needed; am I right here? Arun C

sysfs entries for the character driver

() + device_create() and then create the entries in the folder /sys/class/my_new_class/? Regards, Arun C

Re: Copying user space data to PCI memory

Hi, On Mon, May 18, 2009 at 6:50 AM, Grant Grundler wrote: > Hi Arun, Sandeep, > > On Sat, May 16, 2009 at 06:33:44PM +0530, SandeepKsinha wrote: >> Hi Arun, >> >> On Sat, May 16, 2009 at 5:48 PM, arun c wrote: >> > Hi all, >> > >>

Copying user space data to PCI memory

then can I use copy_to_user(usr_addr, buffer_addr, 1024) also? Regards, Arun C -- To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to ecar...@nl.linux.org Please read the FAQ at http://kernelnewbies.org/FAQ

Re: mutual exclusion locks over PCI memory

Hi, On Mon, Feb 23, 2009 at 1:01 PM, arun c wrote: > Hi, > > On Mon, Feb 23, 2009 at 12:43 PM, Grant Grundler > wrote: >> On Mon, Feb 23, 2009 at 11:47:19AM +0530, arun c wrote: >> ... >>> Yes I don't need any lock to protect my data >>> here

Re: mutual exclusion locks over PCI memory

Hi, On Mon, Feb 23, 2009 at 12:43 PM, Grant Grundler wrote: > On Mon, Feb 23, 2009 at 11:47:19AM +0530, arun c wrote: > ... >> Yes I don't need any lock to protect my data >> here, as host is write only and target is read only. >> >> Here is what I did. >&

Re: mutual exclusion locks over PCI memory

Hi, On Sun, Feb 22, 2009 at 8:25 AM, Grant Grundler wrote: > On Fri, Feb 20, 2009 at 07:10:24AM -0700, Matthew Wilcox wrote: >> On Fri, Feb 20, 2009 at 07:09:51PM +0530, arun c wrote: >> > PCI host machine (PPC cpu) writes commands to >> > the PCI memory space of the

mutual exclusion locks over PCI memory

residing on target memory is used for command exchange. I should not allow host and target to play on the buffer simultaneously in order to avoid corruption. Does anybody know how to implement a lock suitable for this issue? or any lock less algorithm exists for communication over PCI? Regards, Arun

Fwd: PCI communication between host and target.

-- Forwarded message -- From: Peter Teoh Date: Mon, Jan 5, 2009 at 12:00 PM Subject: Re: PCI communication between host and target. To: arun c thank you ... at the moment quite busyoffhand got no answercan u forward to kernelnewbies? many experts are there to help u

PCI communication between host and target.

planning to implement] Anybody has come across similar sort of scenario? Any ideas or any pointers will be highly appreciated. Regards, Arun C -- To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to ecar...@nl.linux.org Please read the FAQ at http://kernelnewbies.org/FAQ

Re: i2c problem with twl4030

> any idea? > > is there any special initialization needed for twl4030? > There is a mailing list for OMAP based boards. "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>, Please ask your question there, don't forget to mention the board name and kernel version yo

How spin_lock_irqsave works?

Hi, The spin_lock_irqsave uses an "unsigned long flags" variable to save the irq state. But if the cpu has more that 64 interrupts, how this save and restore is happening? ( For eg: Arm has 96 interrupts) Regards, Arun C -- To unsubscribe from this list: send an email with &q