> -Original Message-
> From: Benjamin Herrenschmidt [mailto:[EMAIL PROTECTED]
> Sent: Monday, March 24, 2008 3:00 PM
> To: Stephen Neuendorffer
> Cc: Josh Boyer; linuxppc-dev@ozlabs.org; git-dev
> Subject: RE: dcr stuff.
>
>
> On Sun, 2008-03-23 at 21:34
On Sun, 2008-03-23 at 21:34 -0700, Stephen Neuendorffer wrote:
>
> Certainly, if it ain't broke don't fix it. What I'm really trying to
> do is figure out how to clean up alot of non-mainline drivers.
> At the moment, several cores use DCR, but the drivers for those cores
> have internal code fo
-Original Message-
From: Josh Boyer [mailto:[EMAIL PROTECTED]
Sent: Fri 3/21/2008 6:17 PM
To: Stephen Neuendorffer
Cc: linuxppc-dev@ozlabs.org; git-dev
Subject: Re: dcr stuff.
On Fri, 21 Mar 2008 12:05:40 -0700
"Stephen Neuendorffer" <[EMAIL PROTECTED]> wrote:
>
On Fri, 21 Mar 2008 12:05:40 -0700
"Stephen Neuendorffer" <[EMAIL PROTECTED]> wrote:
>
> Is anybody working on the dcr infrastructure?
>
> In particular, there seems to be inconsistency between what the kernel
> does and what ePAPR thinks it should. The code in the kernel selects
> mmio or nati
On Fri, 2008-03-21 at 12:05 -0700, Stephen Neuendorffer wrote:
> Is anybody working on the dcr infrastructure?
>
> In particular, there seems to be inconsistency between what the kernel
> does and what ePAPR thinks it should. The code in the kernel selects
> mmio or native access based on a Kcon
