All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Schwingen <rincewind@discworld.dascon.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Problem with flash cfi legacy mode
Date: Sat, 22 Mar 2008 00:11:51 +0100	[thread overview]
Message-ID: <47E440B7.7010904@discworld.dascon.de> (raw)
In-Reply-To: <NyLtDrlT.1205740722.4117870.tor@localhost>

Tor Krill wrote:
>> Hm - right. You are probably the first one to use that code on a 16-bit
>> non-CFI flash - for 16-bit flashs, the read will need to be changed, but
>> I am not sure how exactly - I think we may need separate code depending
>> on info->chipwidth, because 8-bit flashs only have an 8-bit ID.
>>     
>
> Can one asume that a chip with chipwidht 16 always has an ID of 16bit?
> And how does AMD expanded 3byte id mode fit?  If its safe to just change
> the read   it should be trivial to fix(?)
>   
I think it should be OK to use 16-bit reads if info->chipwidth==2.

cu
Michael

      reply	other threads:[~2008-03-21 23:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-10  9:19 [U-Boot-Users] Problem with flash cfi legacy mode Tor Krill
2008-03-14 21:52 ` Michael Schwingen
2008-03-17  7:58   ` Tor Krill
2008-03-21 23:11     ` Michael Schwingen [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=47E440B7.7010904@discworld.dascon.de \
    --to=rincewind@discworld.dascon.de \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.