From: Ivan Kuten <ivan.kuten@promwad.com>
To: buildroot@busybox.net
Subject: [Buildroot] Adding Cirrus EP93XX ARM to buildroot
Date: Sun, 07 Oct 2007 20:45:48 +0300 [thread overview]
Message-ID: <47091B4C.8090205@promwad.com> (raw)
In-Reply-To: <20071006201536.GH20951@aon.at>
>>>
>>> And submitting patches to mainstream takes long time. And we want Cirrus support now.
>
> Supporting some old version of packages with supplemental patches is
> fine and one thing. Refusing even try to get your additions merged is
> not a proper thing to do IMO.
>
> It is extremely burdensome and impractical to have to patch every single
> "new" upstream release (let alone time-consuming and thus probably
> expensive if somebody pays the time you're spending on doing it).
>
Bernhard, I only wanted to notice that having Cirrus support in buildroot can be
-before- then some of Cirrus patches go in mainline kernel. I'm aware about Cirrus patches
to 2.6.20.4 and 2.6.17.14, and some of our customers still use 2.6.17.14 kernel version.
BR,
Ivan
--------------------------------
Embedded Linux engineer,
Promwad Company: http://www.promwad.com/
Homepage : http://www.ivankuten.com/
--------------------------------
next prev parent reply other threads:[~2007-10-07 17:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-02 21:51 [Buildroot] Adding Cirrus EP93XX ARM to buildroot Brian Austin
2007-10-02 23:42 ` Ivan Kuten
2007-10-03 20:40 ` Bernhard Fischer
2007-10-03 22:54 ` Ivan Kuten
2007-10-04 4:08 ` Ulf Samuelsson
2007-10-04 13:46 ` Brian Austin
2007-10-06 20:15 ` Bernhard Fischer
2007-10-07 17:45 ` Ivan Kuten [this message]
2007-10-07 17:00 ` Bernhard Fischer
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=47091B4C.8090205@promwad.com \
--to=ivan.kuten@promwad.com \
--cc=buildroot@busybox.net \
/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.