Olof Johansson wrote:
> Having been in a similar situation myself (needing to share resources
> between DMA, ethernet and function offload), I recommend creating a
> separate small library that all those drivers use, instead of making
> some sort of dependency between drivers in completely differe
On Thu, Jan 10, 2008 at 05:12:16PM -0600, Timur Tabi wrote:
> Grant Likely wrote:
>
> > Does the driver access the DMA and GUTS registers directly? If so,
> > what do you have to protect against race conditions of other drivers
> > accessing them also.
>
> I don't have any more protection than a
Grant Likely wrote:
>> As for the GUTS driver, well, I just program a few registers at startup, and
>> I
>> don't think any other driver touches them.
>
> Okay; at some point in the future they'll need to be accessed from a
> common routine too.
I'll add that to my to-do list.
--
Timur Tabi
L
On 1/10/08, Timur Tabi <[EMAIL PROTECTED]> wrote:
> Grant Likely wrote:
>
> > Does the driver access the DMA and GUTS registers directly? If so,
> > what do you have to protect against race conditions of other drivers
> > accessing them also.
>
> I don't have any more protection than any other dri
Grant Likely wrote:
> Does the driver access the DMA and GUTS registers directly? If so,
> what do you have to protect against race conditions of other drivers
> accessing them also.
I don't have any more protection than any other driver that accesses SOC
registers directly. Last I heard, Zhan
