From: Richard Retanubun <RichardRetanubun@RuggedCom.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] CFI: geometry reversal for STMicro M29W320DT
Date: Thu, 19 Mar 2009 09:50:25 -0400 [thread overview]
Message-ID: <49C24DA1.4080508@RuggedCom.com> (raw)
In-Reply-To: <200903090930.01771.sr@denx.de>
Hi Stefan,
Just following up on this patch, the only other action I've seen on with regards to this is to fake the device
identification from top-boot to bottom boot, but I think this is more 'masking' the problem and
I don't have enough visibility to see if it is a safe thing to do.
In any case, even the reversal from top-boot to bottom-boot still
needs identification on a chip-per-chip basis.
In any case, I'd like to know if this patch is [ACK|NACK]?
Many thanks for your time.
- Richard
next prev parent reply other threads:[~2009-03-19 13:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-06 15:09 [U-Boot] [PATCH] CFI: geometry reversal for STMicro M29W320DT Richard Retanubun
2009-03-06 15:27 ` Stefan Roese
2009-03-06 16:30 ` Richard Retanubun
2009-03-09 8:30 ` Stefan Roese
2009-03-19 13:50 ` Richard Retanubun [this message]
2009-03-19 13:59 ` Stefan Roese
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=49C24DA1.4080508@RuggedCom.com \
--to=richardretanubun@ruggedcom.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox