From: Dmitry Baryshkov <dbaryshkov@gmail.com>
To: openembedded-devel@openembedded.org
Subject: [RFC] Tosa patches for 2.6.24
Date: Mon, 28 Jan 2008 00:05:23 +0000 (UTC) [thread overview]
Message-ID: <fnj683$oaa$5@ger.gmane.org> (raw)
Hi,
As some of you know, currently I work on improving the Sharp SL-6000 (tosa)
kernel support. Some parts are going to be merged RSN, some parts are still
in preparation to submission. A pile of patches can't be submitted because
of backwards dependencies. Currently my patchset contains 54 patches.
Now back to support of tosa in OE. I think I have several options:
0) linux-rp-2.6.23 contains support for the device. It has problems, but it's
mostly working. So leave it just for now, don't touch 2.6.24 and wait for
2.6.25.
I would prefer not to follow this path as I want to enlarge testing base
for patchset and to let tosa-owners use decent kernel features.
1) Add all my patches on the top of linux-rp-2.6.24 as the tosa-specific part.
This can be hard, as I touch various bits of kernel, this can require
major efforts.
2) Just start linux-tosa recipe branch, importing few patches from linux-rp,
and merge them later.
No major pros et contras.
What would you recommend?
--
With best wishes
Dmitry
next reply other threads:[~2008-01-28 0:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-28 0:05 Dmitry Baryshkov [this message]
2008-01-28 0:37 ` [RFC] Tosa patches for 2.6.24 Richard Purdie
2008-01-28 7:22 ` Marcin Juszkiewicz
2008-01-28 13:25 ` Dmitry Baryshkov
2008-01-28 13:37 ` Marcin Juszkiewicz
2008-01-30 14:00 ` Dmitry Baryshkov
2008-01-28 23:28 ` Paul Sokolovsky
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='fnj683$oaa$5@ger.gmane.org' \
--to=dbaryshkov@gmail.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@openembedded.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.