From: Sergey Lapin <slapin@ossfans.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC][PULL-REQ] MTD update
Date: Sat, 29 Dec 2012 19:35:38 -0500 [thread overview]
Message-ID: <20121230003538.GD9924@build.ihdev.net> (raw)
In-Reply-To: <20121229233331.B2291200FB7@gemini.denx.de>
On Sun, Dec 30, 2012 at 12:33:31AM +0100, Wolfgang Denk wrote:
> Dear Sergey Lapin,
>
> In message <20121229231332.GC9924@build.ihdev.net> you wrote:
> >
> > > > Tom is right when asking to use a stable kernel tree version as
> > > > starting point. Said "interesting changes" may be added in a second
> > > > step, once we have proven that the stable code is actually working
> > > > stable for us, too.
> > > OK, will rebase.
> > Well, I reviewed the difference with 3.7.1 and 3.8-rc's MTD,
> > and I see some changes I critically depend on. These are very small, though.
> > The rest can be added for completeness. I can make these changes into separate
> > patch, will it be fine with you?
>
> Ideally you should come up with a workign implementation based on the
> current stable tree. The locate any additional commits in Linux that
> are needed / useful from your point of view, and check if these can be
> applied _directly_ (i. e. the unmodified Linux commits) to the U-Boot
> tree. If we can do this, any future updates will be much easier, so
> this is a good test for the benefits of the new version.
Well, direct application of Linux's commits will not work mostly because
lower level functions like timers have slightly different implementations.
If we'd implement jiffies and associated macros in u-boot, that'd be awesome,
but maybe an overkill, and is also out of scope of these patches and not in
field of my interests. Simple things, like constant changes will work,
but code changes in nand_base.c won't work I'm afraid.
>
> Best regards,
>
> Wolfgang Denk
>
> --
> DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
> HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
> Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
> Let's say the docs present a simplified view of reality... :-)
> - Larry Wall in <6940@jpl-devvax.JPL.NASA.GOV>
next prev parent reply other threads:[~2012-12-30 0:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-28 12:17 [U-Boot] [RFC][PULL-REQ] MTD update Sergey Lapin
2012-12-28 13:51 ` Wolfgang Denk
2012-12-28 15:07 ` Sergey Lapin
2012-12-28 15:14 ` Wolfgang Denk
2012-12-28 13:59 ` Tom Rini
2012-12-29 20:54 ` Sergey Lapin
2012-12-29 21:03 ` Marek Vasut
2012-12-29 21:52 ` Wolfgang Denk
2012-12-29 22:20 ` Sergey Lapin
2012-12-29 23:13 ` Sergey Lapin
2012-12-29 23:21 ` Marek Vasut
2012-12-29 23:33 ` Wolfgang Denk
2012-12-30 0:35 ` Sergey Lapin [this message]
2012-12-30 2:54 ` Vikram Narayanan
2013-01-02 15:33 ` Tom Rini
2013-01-03 3:22 ` Scott Wood
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=20121230003538.GD9924@build.ihdev.net \
--to=slapin@ossfans.org \
--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