Janne Johansson wrote:
>> 2011/4/3 Claudio Jeker
>>
>> bce(4) was turned off because of limitations in the DMA engine that allows
>> the chip to access only 1G of memory. On systems with more then 1G of
>> memory hilarity ensued.
>>
>> Now I rewrote the driver to use bcopy() to copy the mbufs into
2011/4/3 Claudio Jeker
> bce(4) was turned off because of limitations in the DMA engine that allows
> the chip to access only 1G of memory. On systems with more then 1G of
> memory hilarity ensued.
>
> Now I rewrote the driver to use bcopy() to copy the mbufs into a savely
> allocated DMA memory
> From: David Gwynne
> Date: Mon, 4 Apr 2011 05:59:20 +1000
>
> On 04/04/2011, at 5:31 AM, Mark Kettenis wrote:
>
> >> Date: Sun, 3 Apr 2011 13:46:40 +0200
> >> From: Claudio Jeker
> >>
> >> bce(4) was turned off because of limitations in the DMA engine that allows
> >> the chip to access only
On 04/04/2011, at 5:31 AM, Mark Kettenis wrote:
>> Date: Sun, 3 Apr 2011 13:46:40 +0200
>> From: Claudio Jeker
>>
>> bce(4) was turned off because of limitations in the DMA engine that allows
>> the chip to access only 1G of memory. On systems with more then 1G of
>> memory hilarity ensued.
>>
> Date: Sun, 3 Apr 2011 13:46:40 +0200
> From: Claudio Jeker
>
> bce(4) was turned off because of limitations in the DMA engine that allows
> the chip to access only 1G of memory. On systems with more then 1G of
> memory hilarity ensued.
>
> Now I rewrote the driver to use bcopy() to copy the mb
bce(4) was turned off because of limitations in the DMA engine that allows
the chip to access only 1G of memory. On systems with more then 1G of
memory hilarity ensued.
Now I rewrote the driver to use bcopy() to copy the mbufs into a savely
allocated DMA memory buffer. So the chip will now work wi
