mail archive of the barebox mailing list
 help / color / mirror / Atom feed
* MTD NAND updates
@ 2012-05-31 16:31 Dirk Hörner
  2012-05-31 17:01 ` Sascha Hauer
  0 siblings, 1 reply; 2+ messages in thread
From: Dirk Hörner @ 2012-05-31 16:31 UTC (permalink / raw)
  To: barebox


[-- Attachment #1.1: Type: text/plain, Size: 565 bytes --]

Hi List,

while going through the NAND specific parts of the MTD layer I noticed that
there are quite a few updates available from recent Linux kernel versions:
 * detection of flashes via ONFI
 * improved detection of flashes via extid
 * added device id's in the hard-coded table

I'd like to provide some patches, just a few questions:
 * should I base them on master or next?
 * should I try to cherry-pick updates from the kernel or should I just
merge stuff from the kernel and send patches split into logical parts
(onfi, extid, id additions)?

Thanks,
Dirk

[-- Attachment #1.2: Type: text/html, Size: 716 bytes --]

[-- Attachment #2: Type: text/plain, Size: 149 bytes --]

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: MTD NAND updates
  2012-05-31 16:31 MTD NAND updates Dirk Hörner
@ 2012-05-31 17:01 ` Sascha Hauer
  0 siblings, 0 replies; 2+ messages in thread
From: Sascha Hauer @ 2012-05-31 17:01 UTC (permalink / raw)
  To: Dirk Hörner; +Cc: barebox

Hi Dirk,

On Thu, May 31, 2012 at 06:31:20PM +0200, Dirk Hörner wrote:
> Hi List,
> 
> while going through the NAND specific parts of the MTD layer I noticed that
> there are quite a few updates available from recent Linux kernel versions:
>  * detection of flashes via ONFI
>  * improved detection of flashes via extid
>  * added device id's in the hard-coded table
> 
> I'd like to provide some patches, just a few questions:
>  * should I base them on master or next?

master is fine. I'll handle the conflicts if necessary.

>  * should I try to cherry-pick updates from the kernel or should I just
> merge stuff from the kernel and send patches split into logical parts
> (onfi, extid, id additions)?

Splitting into logical parts seems to make the most sense. If it's just
a single patch you can also cherry-pick it, but we don't need the whole
feature-add-then-several-bugfixes history.

Sascha

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2012-05-31 17:01 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2012-05-31 16:31 MTD NAND updates Dirk Hörner
2012-05-31 17:01 ` Sascha Hauer

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox