From: jacmet@sunsite.dk (Peter Korsgaard)
To: linux-arm-kernel@lists.infradead.org
Subject: Samsung S3C6410 mainline merge coordination
Date: Wed, 02 Sep 2009 14:49:00 +0200 [thread overview]
Message-ID: <873a75pl4z.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <20090902031719.GK3838@prithivi.gnumonks.org> (Harald Welte's message of "Wed\, 2 Sep 2009 12\:17\:19 +0900")
>>>>> "Harald" == Harald Welte <laforge@gnumonks.org> writes:
Hi,
Harald> === NAND ===
Harald> * mainline currently uses same driver for s3c24xx and s3c64xx
Harald> ** samsung uses a new driver for 2450, 6400, 6410 (and later)
Harald> * does it make sense to extend the mainline driver with new SoC support
Harald> or should we rather split the mainline driver?
The nand controllers in the different variants are afaik very similar,
that's why I added 64xx support to s3c2410.c. What would a split gain
us?
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2009-09-02 12:49 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-02 3:17 Samsung S3C6410 mainline merge coordination Harald Welte
2009-09-02 9:51 ` Nelson Castillo
2009-09-02 12:15 ` Harald Welte
2009-09-02 15:58 ` Nelson Castillo
2009-09-02 10:05 ` Mark Brown
2009-09-02 12:11 ` Harald Welte
2009-09-02 13:44 ` jassi brar
2009-09-02 14:47 ` Mark Brown
2009-09-03 0:38 ` jassi brar
2009-09-03 12:14 ` Mark Brown
2009-09-03 13:39 ` jassi brar
2009-09-03 15:18 ` Mark Brown
2009-09-04 1:08 ` jassi brar
2009-09-04 13:41 ` Mark Brown
2009-09-04 14:27 ` jassi brar
2009-09-04 14:57 ` Mark Brown
2009-09-04 1:27 ` Samsung SoC ASOC drivers Harald Welte
2009-09-04 4:10 ` jassi brar
2009-09-02 19:09 ` Samsung S3C6410 mainline merge coordination Ben Dooks
2009-09-03 0:21 ` Joonyoung Shim
2009-09-03 11:06 ` Mark Brown
2009-09-03 12:48 ` Joonyoung Shim
2009-09-02 13:45 ` Mark Brown
2009-09-02 19:22 ` Ben Dooks
[not found] ` <19987914.1168001251884594226.JavaMail.coremail@bj126app54.126.com>
2009-09-02 12:01 ` Harald Welte
2009-09-02 19:10 ` Ben Dooks
2009-09-02 22:26 ` Harald Welte
2009-09-03 9:51 ` Daniel Silverstone
2009-09-03 10:34 ` Russell King - ARM Linux
2009-09-03 10:40 ` Daniel Silverstone
2009-09-04 5:48 ` Pavel Machek
2009-09-02 12:03 ` David F. Carlson
2009-09-02 12:46 ` Peter Korsgaard
2009-09-02 19:16 ` Ben Dooks
2009-09-03 1:56 ` Harald Welte
2009-09-03 10:04 ` Peter Korsgaard
2009-09-03 10:57 ` Mark Brown
[not found] ` <7641737.122161251944382753.JavaMail.coremail@bj126app17.126.com>
2009-09-03 4:31 ` Harald Welte
2009-09-10 5:49 ` Samsung S3C6410 / SmartQ / 2D acceleration / Xorg Harald Welte
2009-09-15 23:34 ` Ben Dooks
2009-09-15 9:49 ` Samsung S3C6410 / SmartQ / 2D acceleration / Xorgy David F. Carlson
2009-09-02 12:49 ` Peter Korsgaard [this message]
2009-09-02 22:30 ` Samsung S3C6410 mainline merge coordination Harald Welte
2009-09-02 16:12 ` Ben Dooks
2009-09-02 21:25 ` David F. Carlson
2009-09-02 23:18 ` Harald Welte
2009-09-03 3:31 ` Bill Gatliff
2009-09-03 3:38 ` Nelson Castillo
2009-09-03 4:33 ` Harald Welte
2009-09-04 7:15 ` Nelson Castillo
2009-09-02 16:58 ` Mark Brown
[not found] <23992600.419641251935757361.JavaMail.weblogic@epml11>
2009-09-03 0:46 ` Harald Welte
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=873a75pl4z.fsf@macbook.be.48ers.dk \
--to=jacmet@sunsite.dk \
--cc=linux-arm-kernel@lists.infradead.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.