David Woodhouse <[EMAIL PROTECTED]> writes:
> On 22 Mar 2001, Eric W. Biederman wrote:
>
> > In practice if something like the jedec is going to be provided it
> > probably should work like the cfi driver and pass control over to the
> > to the command set drivers. I don't think AMD and Intel actually
> > changed their command sets when moving to cfi. At least nothing
> > beyond extending them.
>
> Someone just merged it so it does. I haven't looked at the result yet.
I'll have to look then. I think a few of my bugfixes will actually
apply to the AMD command set driver. Last I looked the AMD command
set driver didn't respect bit width, and does more than
just a byte read/write when doing commands. Since I only had a single
byte data channel to my memory that made me pretty nervous.
I deliberately didn't implement anything bigger than byte wide access
in my mapping driver besides the memcpy functions, so a driver that didn't
respect the bit width would get an oops. Is this the right way to
handle this situtation?
Eric
