From: Johannes Berg <johannes@sipsolutions.net>
To: Kalle Valo <kalle.valo@iki.fi>
Cc: Bharat Bhushan <bharat.b.bhushan@gmail.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: porting open source mac to linux 2.6.13.0
Date: Thu, 22 Jan 2009 15:54:20 +0100 [thread overview]
Message-ID: <1232636060.4224.16.camel@johannes.local> (raw)
In-Reply-To: <87eiyvl8ex.fsf@litku.valot.fi> (sfid-20090122_153106_546807_B2AA31E6)
[-- Attachment #1: Type: text/plain, Size: 755 bytes --]
On Thu, 2009-01-22 at 16:31 +0200, Kalle Valo wrote:
> > Then cancel the contract with your embedded vendor and find a decent
> > one.
>
> Just out of curiousity, is there an embedded vendor who adds support
> to the mainline kernels and maintains it? To me it looks like more or
> less everyone want to fork their own kernel and then forget it.
Depends what you mean by "maintain", and what you're looking for. I know
many powerpc boards are supported in the kernel, so if you look in that
space I'm sure you'll find something. I don't think you'll find a vendor
that maintains their entire range of boards very long into the future,
but once it's in the kernel it's much less likely to break, and if it
does easier to fix.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2009-01-22 14:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-22 5:24 porting open source mac to linux 2.6.13.0 Bharat Bhushan
2009-01-22 8:02 ` Holger Schurig
2009-01-22 10:53 ` Johannes Berg
2009-01-22 14:31 ` Kalle Valo
2009-01-22 14:54 ` Johannes Berg [this message]
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=1232636060.4224.16.camel@johannes.local \
--to=johannes@sipsolutions.net \
--cc=bharat.b.bhushan@gmail.com \
--cc=kalle.valo@iki.fi \
--cc=linux-wireless@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox