[PATCH 2.6] pSeries_pci.c replace pci_find_device with pci_get_device

[PATCH 2.6] pSeries_pci.c replace pci_find_device with pci_get_device

[Hanna Linder]

As pci_find_device is going away I've replaced it with pci_get_device.
If someone with a PPC64 system could test it I would appreciate it.

Thanks.

Hanna Linder
IBM Linux Technology Center

Signed-off-by: Hanna Linder <hannal@us.ibm.com>

---
diff -Nrup linux-2.6.9-rc3-mm3cln/arch/ppc64/kernel/pSeries_pci.c linux-2.6.9-rc3-mm3patch3/arch/ppc64/kernel/pSeries_pci.c
--- linux-2.6.9-rc3-mm3cln/arch/ppc64/kernel/pSeries_pci.c	2004-10-07 15:54:30.000000000 -0700
+++ linux-2.6.9-rc3-mm3patch3/arch/ppc64/kernel/pSeries_pci.c	2004-10-08 10:24:00.064501400 -0700
@@ -646,7 +646,7 @@ void __init pSeries_final_fixup(void)
 
 	check_s7a();
 
-	while ((dev = pci_find_device(PCI_ANY_ID, PCI_ANY_ID, dev)) != NULL) {
+	for_each_pci_dev(dev) {
 		pci_read_irq_line(dev);
 		if (s7a_workaround) {
 			if (dev->irq > 16) {

character device interface to existing socket interface.

[shankar krishnamurthy]

I am looking for help in writing character 
device interface for existing socket interface.

Planning to write as kernel module. Kernel 2.4.20. 
It will be a simple pass through to the socket. I mean
it sits above socket and whatever user gives, the 
driver passes it to socket and vice versa. In that
sense its pass-through or a psuedo driver.

When user creates the device, he gives already 
connected socket to device driver. Once device
gets created, user closes the socket!

My hunch is that this looks so common that somebody
would have already written or have some pointer to it.

Somebody may wonder why one needs this ...but for
we can take it as *application specific* requirement.

Please let me know if you know anything about it.


		
__________________________________
Do you Yahoo!?
Read only the mail you want - Yahoo! Mail SpamGuard.
http://promotions.yahoo.com/new_mail 

Re: character device interface to existing socket interface.

[Neil Horman]

shankar krishnamurthy wrote:
> I am looking for help in writing character 
> device interface for existing socket interface.
> 
> Planning to write as kernel module. Kernel 2.4.20. 
> It will be a simple pass through to the socket. I mean
> it sits above socket and whatever user gives, the 
> driver passes it to socket and vice versa. In that
> sense its pass-through or a psuedo driver.
> 
> When user creates the device, he gives already 
> connected socket to device driver. Once device
> gets created, user closes the socket!
> 
> My hunch is that this looks so common that somebody
> would have already written or have some pointer to it.
> 
> Somebody may wonder why one needs this ...but for
> we can take it as *application specific* requirement.
> 
> Please let me know if you know anything about it.
> 
> 
> 		
> __________________________________
> Do you Yahoo!?
> Read only the mail you want - Yahoo! Mail SpamGuard.
> http://promotions.yahoo.com/new_mail 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
Something pretty close has already been done in the driver for 
/dev/inet/[tcp|udp|icmp|etc].
Neil

-- 
/***************************************************
  *Neil Horman
  *Software Engineer
  *Red Hat, Inc.
  *nhorman@redhat.com
  *gpg keyid: 1024D / 0x92A74FA1
  *http://pgp.mit.edu
  ***************************************************/