From: Luca Tettamanti <kronos.it@gmail.com>
To: Jay Cliburn <jacliburn@bellsouth.net>
Cc: kronos.it@gmail.com, Chris Snook <csnook@redhat.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4] atl1: Revised Attansic L1 ethernet driver
Date: Sat, 25 Nov 2006 23:43:58 +0100 [thread overview]
Message-ID: <20061125224358.GA29403@dreamland.darkstar.lan> (raw)
In-Reply-To: <20061121202541.GA23036@dreamland.darkstar.lan>
Hello,
Luca Tettamanti <kronos.it@gmail.com> ha scritto:
> Chris Snook <csnook@redhat.com> ha scritto:
>>
>> I've been working on this with Jay since his initial submission. Thanks
>> to everyone who has provided feedback on the resubmit. We're currently
>> quite short on actual testers, since the chip only seems to be on Asus
>> M2V motherboards at present. Please let me and Jay know if you have one
>> of these boards and would like to test and/or have encountered bugs.
>
> Asus P5B-E also has L1 chip. I'll get the board in a few days and I'll
> test whatever patch you throw at me ;)
Got the board, done some basic testing: so far so good :)
The controller also supports MSI and (at least with my chipset - G965)
it works fine:
218: 80649 0 PCI-MSI-edge eth1
which is nice, otherwise it ends up sharing the IRQ with SATA and USB.
I also have a small patch:
On probe failure and on removal the device should be disabled:
Signed-Off-By: Luca Tettamanti <kronos.it@gmail.com>
---
drivers/net/atl1/atl1_main.c | 8 ++++++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/drivers/net/atl1/atl1_main.c b/drivers/net/atl1/atl1_main.c
index 167e28c..4883111 100644
--- a/drivers/net/atl1/atl1_main.c
+++ b/drivers/net/atl1/atl1_main.c
@@ -2224,14 +2224,14 @@ static int __devinit at_probe(struct pci
printk(KERN_DEBUG
"%s: no usable DMA configuration, aborting\n",
at_driver_name);
- return err;
+ goto err_dma;
}
pci_using_64 = false;
}
/* Mark all PCI regions associated with PCI device
* pdev as being reserved by owner at_driver_name */
if ((err = pci_request_regions(pdev, at_driver_name)))
- return err;
+ goto err_request_regions;
/* Enables bus-mastering on the device and calls
* pcibios_set_master to do the needed arch specific settings */
pci_set_master(pdev);
@@ -2384,6 +2384,9 @@ static int __devinit at_probe(struct pci
free_netdev(netdev);
err_alloc_etherdev:
pci_release_regions(pdev);
+ err_request_regions:
+ err_dma:
+ pci_disable_device(pdev);
return err;
}
@@ -2410,6 +2413,7 @@ static void __devexit at_remove(struct p
iounmap(adapter->hw.hw_addr);
pci_release_regions(pdev);
free_netdev(netdev);
+ pci_disable_device(pdev);
}
static int at_suspend(struct pci_dev *pdev, pm_message_t state)
Luca
--
Not an editor command: Wq
next prev parent reply other threads:[~2006-11-25 22:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-19 20:28 [PATCH 0/4] atl1: Revised Attansic L1 ethernet driver Jay Cliburn
2006-11-20 1:15 ` Alan
2006-11-20 6:34 ` Chris Snook
2006-11-20 9:46 ` Alan
2006-11-20 6:37 ` Chris Snook
2006-11-21 20:25 ` Luca Tettamanti
2006-11-25 22:43 ` Luca Tettamanti [this message]
2006-11-26 1:33 ` Jay Cliburn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20061125224358.GA29403@dreamland.darkstar.lan \
--to=kronos.it@gmail.com \
--cc=csnook@redhat.com \
--cc=jacliburn@bellsouth.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).