public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] NAND support [was: Port U-Boot to SBC-2410X]
Date: Thu, 01 Sep 2005 01:05:54 +0200	[thread overview]
Message-ID: <20050831230554.6DA17352687@atlas.denx.de> (raw)
In-Reply-To: Your message of "Wed, 31 Aug 2005 23:21:22 +0200." <20050831212122.GA32559@orphique>

Dear Ladislav,

in message <20050831212122.GA32559@orphique> you wrote:
> 
> I promised you to send update over a weekend, but didn't tell you which
> one ;-). Although normaly I do not have problems explaining my boss why

I know how this goes. Been there before. Can't remember when for  the
first time :-(

> Patch against "testing-NAND" branch can be found here:
> ftp://ftp.linux-mips.org/pub/linux/mips/people/ladis/u-boot/u-boot-nand.diff

Can you please either send this by e-mail, or put it on a server that
actually works?

> It also contains support for new board NetStar (it is not meant to be
> included - I want to maintain it outside U-Boot, but I'd agree to put it
> into "testing-NAND" branch for reference), which shows sample

If I add it to "testing-NAND" (and it makes a lot of sense if this is
a working example) then it will go more or  less  automagically  into
the main tree as soon as I merge branches. Is this acceptable to you?

> implementation. Note that you have to define CONFIG_NEW_NAND_CODE to
> actually compile and use new code. Original <linux/mtd/nand.h> was moved
> to <linux/mtd/nand_old.h> and so has to be fixed all unconverted boards
> includes (I do not have energy to do it now and test if they still compiles).

We will have to go through this when switching the code base.

> Ideally old and new code should be able to coexist. Please let me know if you

But only one version shall be in the main branch at a time, i. e. one
day the new code will replace the old one, and then all  boards  will
need to be converted.

> experience any problems or if you want me to split patch into smaller
> chunks.

Will do when I can lay my hands on the patch; keep  getting  timeouts
only :-(

> (*) - needs discussion and improvements, it's not finished.

Thanks for providing a sound base for this discussion.

Best regards,

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
One difference between a man and a machine is that a machine is quiet
when well oiled.

  reply	other threads:[~2005-08-31 23:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-31 13:55 [U-Boot-Users] Port U-Boot to SBC-2410X luo.jinhua
2005-08-31 15:19 ` Wolfgang Denk
2005-08-31 21:21   ` [U-Boot-Users] NAND support [was: Port U-Boot to SBC-2410X] Ladislav Michl
2005-08-31 23:05     ` Wolfgang Denk [this message]
2005-09-01  8:21       ` Ladislav Michl
2005-09-01  1:40   ` [U-Boot-Users] Port U-Boot to SBC-2410X luo.jinhua

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=20050831230554.6DA17352687@atlas.denx.de \
    --to=wd@denx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox