| To: | Pekka Pietikainen <pp@xxxxxxxxxx> |
|---|---|
| Subject: | Re: Dealing with buggy hardware (was: b44 and 4g4g) |
| From: | Pavel Machek <pavel@xxxxxxx> |
| Date: | Thu, 10 Jun 2004 22:05:04 +0200 |
| Cc: | "David S. Miller" <davem@xxxxxxxxxx>, netdev@xxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx |
| In-reply-to: | <20040609122905.GA12715@xxxxxxxxxx> |
| References: | <20040531202104.GA8301@xxxxxxxxxx> <20040605200643.GA2210@xxxxxxxxxx> <20040605131923.232f8950.davem@xxxxxxxxxx> <20040609122905.GA12715@xxxxxxxxxx> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
| User-agent: | Mutt/1.3.27i |
Hi!
> > > + if(virt_to_bus(skb->data) + skb->len > B44_PCI_DMA_MAX) {
> >
> > You can't use this non-portable interface, you have to:
> >
> > 1) pci_map the data
> > 2) test the dma_addr_t returned
> Ok, fixed. Certainly not ideal, but should fix things for those with
> problems (ie. running the 4G4G patch) and work as before for everyone else.
>
This should hit machines with 2GB ram too, right?
Is it possible to find if it hits me? I get hard lockups on
2GB machine with b44, but they take ~5min.. few hours to
reproduce...
It seems to me like this should hit very quickly.
--
64 bytes from 195.113.31.123: icmp_seq=28 ttl=51 time=448769.1 ms
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Dealing with buggy hardware (was: b44 and 4g4g), Pekka Pietikainen |
|---|---|
| Next by Date: | Re: [PATCH] dst allocation problem in ndisc, Shirley Ma |
| Previous by Thread: | Re: Dealing with buggy hardware (was: b44 and 4g4g), Pekka Pietikainen |
| Next by Thread: | Re: Dealing with buggy hardware (was: b44 and 4g4g), Pekka Pietikainen |
| Indexes: | [Date] [Thread] [Top] [All Lists] |