This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: Intel 28fxxx flash driver
- To: Jonathan Larmour <jlarmour at redhat dot com>
- Subject: Re: [ECOS] Intel 28fxxx flash driver
- From: Jesper Skov <jskov at redhat dot com>
- Date: Thu, 18 Oct 2001 08:23:34 +0200
- Cc: Ian Campbell <icampbell at arcom dot co dot uk>,eCos List <ecos-discuss at sources dot redhat dot com>,Jesper Skov <jskov at redhat dot com>, dhowells at redhat dot com
- References: <1003328357.10305.22.camel@LinuxDev><3BCDF396.D15E7EB1@redhat.com>
>>>>> "Jonathan" == Jonathan Larmour <jlarmour@redhat.com> writes:
Jonathan> Ian Campbell wrote:
>> Hi,
>>
>> I am looking at adding support for a flash chip in the 28Fxxx
>> family and was looking over the existing definitions in
>> devs/flash/intel/28fxxx/.../flash_28fxxx_parts.inl.
>>
>> I happened to notice that the 28F320C3 entry puts the start of the
>> boot block at 0x3e0000, which is 0x1f0000 in the 16-bit address,
>> space of the chip. From my reading of the manual the boot block
>> actually starts at address 0x1f8000 which == 0x3f0000. Is this a
>> bug or have I misunderstood something? (Perhaps someones eye
>> slipped down a line when they were reading the memory map table?)
Jonathan> Looking at the Intel docs, I agree. I'll make the change
Jonathan> internally. If Jesper disagrees he can always shout
Jonathan> :-). It's probably just that no-one ever tried to program
Jonathan> the parameter blocks.
That's a bug. I think David is probably using the -B variant of the
part.
Jesper