From: "Daryl Van Vorst" <daryl@wideray.com>
To: "'Marcel Holtmann'" <marcel@holtmann.org>,
"'Aaron Klish'" <aklish1@urbana.css.mot.com>
Cc: "'BlueZ Mailing List'" <bluez-devel@lists.sourceforge.net>
Subject: RE: [Bluez-devel] New Bluetooth kernel patches available
Date: Fri, 19 Dec 2003 10:00:00 -0800 [thread overview]
Message-ID: <000201c3c659$ecd16240$1a01010a@baked> (raw)
In-Reply-To: <1071764167.2866.75.camel@pegasus>
Marcel,
WideRay will be using the 2.4.18 and 2.4.21 patches for some time. The
2.4.21 patches are more important to us than the 2.4.18 patches. 2.4.21
appears to be the latest 2.4 series kernel for which there are arm =
(xscale)
patches available.
I realize the 2.4.18 kernel is getting pretty old... But it doesn't =
hurt to
ask. ;)
-Daryl.
> -----Original Message-----
> From: bluez-devel-admin@lists.sourceforge.net=20
> [mailto:bluez-devel-admin@lists.sourceforge.net] On Behalf Of=20
> Marcel Holtmann
> Sent: December 18, 2003 8:16 AM
> To: Aaron Klish
> Cc: BlueZ Mailing List
> Subject: Re: [Bluez-devel] New Bluetooth kernel patches available
>=20
>=20
> Hi Aaron,
>=20
> > Motorola will use the 2.4.20 patches for sometime. We'd=20
> appreciate=20
> > it if you could continue to maintain that line. Thanks.
>=20
> so what to do next?
>=20
> Sharp Zaurus (ROM 3.10) 2.4.18
> Familiar Linux v0.7.x 2.4.19
> Motorola 2.4.20
> OpenZaurus 2.4.21
> Most desktops 2.4.22
> Latest stable 2.4.23
>=20
> For now the latest patch versions are proven to be rock solid=20
> and I hope we don't need any further updates in future. But=20
> as all of us already know, nobody is perfect.
>=20
> Regards
>=20
> Marcel
>=20
>=20
>=20
>=20
> -------------------------------------------------------
> This SF.net email is sponsored by: IBM Linux Tutorials.
> Become an expert in LINUX or just sharpen your skills. Sign=20
> up for IBM's Free Linux Tutorials. Learn everything from the=20
> bash shell to sys admin. Click now!=20
> http://ads.osdn.com/?ad_id=3D1278&alloc_id=3D3371> &op=3Dclick
>=20
> _______________________________________________
>=20
> Bluez-devel mailing list
> Bluez-devel@lists.sourceforge.net=20
> https://lists.sourceforge.net/lists/listinfo/b> luez-devel
>=20
next prev parent reply other threads:[~2003-12-19 18:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-15 16:30 [Bluez-devel] New Bluetooth kernel patches available Marcel Holtmann
2003-12-15 16:58 ` Stephen Crane
2003-12-15 22:41 ` Marcel Holtmann
2003-12-16 9:22 ` Matthias Thomae
2003-12-16 9:40 ` Stephen Crane
2003-12-18 14:57 ` Aaron Klish
2003-12-18 16:16 ` Marcel Holtmann
2003-12-18 17:49 ` Aaron Klish
2003-12-18 17:53 ` Aaron Klish
2003-12-18 18:03 ` Marcel Holtmann
2003-12-19 18:00 ` Daryl Van Vorst [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-03-15 23:30 Marcel Holtmann
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='000201c3c659$ecd16240$1a01010a@baked' \
--to=daryl@wideray.com \
--cc=aklish1@urbana.css.mot.com \
--cc=bluez-devel@lists.sourceforge.net \
--cc=marcel@holtmann.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.