From: Pantelis Antoniou <panto@intracom.gr>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] New NAND code
Date: Mon, 02 Aug 2004 11:27:46 +0300 [thread overview]
Message-ID: <410DFB02.5040105@intracom.gr> (raw)
In-Reply-To: <006701c47869$22540f50$0212000a@PCSTEFAN>
Stefan Roese wrote:
> Hello!
>
>
>>>I was just wondering about state of the NAND code. When I remember
>>>correctly a pretty big rewrite was done but not commited yet. Is the
>>>last patch sent to this list from Pantelis Antoniou on 5th
>>
>>May still the
>>
>>>latest version?
>>
>>Did anybody actually test this rewrite extensively? I don't remember
>>any feedback?
>
>
> I just searched the archieve:
> Dave Ellis gave a feedback (3rd May) for an earlier version of the
> rewritten code. And Wolfgang Denk mentioned on 7th June that the code
> doesn't compile (for the PPChameleon Board).
>
> Right now the patch from 5th May doesn't even apply to the current CVS.
>
> Pantelis or Dave, could you give us any info about the status of the
> code? Are you still using your patch? Is there a newer version that
> applies to the current CVS? I am willing to do some testing...
>
> Best regards,
> Stefan
>
>
>
I'm using the code extensively on my boards.
There is one more thing in my TODO list; support large Samsung NANDs.
Unfortunately not much feedback was received from other users of NAND.
If I can scrape some time I'll send a patch against the current CVS.
I sure could use a tester though :)
Regards
Pantelis
next prev parent reply other threads:[~2004-08-02 8:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-16 17:25 [U-Boot-Users] New NAND code Stefan Roese
2004-08-01 22:45 ` Wolfgang Denk
2004-08-02 8:17 ` Stefan Roese
2004-08-02 8:27 ` Pantelis Antoniou [this message]
2004-08-10 10:13 ` Andy Hawkins
2004-08-02 8:50 ` Wolfgang Denk
2005-06-07 15:10 ` Ladislav Michl
2005-06-07 20:22 ` Wolfgang Denk
2006-08-10 6:22 ` rahul
-- strict thread matches above, loose matches on Subject: below --
2004-08-03 13:33 Dave Ellis
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=410DFB02.5040105@intracom.gr \
--to=panto@intracom.gr \
--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