From: "durai" <durai@isofttech.com>
To: "BlueZ Mailing List" <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] support for CSR Bluecore4 chip
Date: Thu, 7 Apr 2005 13:09:33 +0530 [thread overview]
Message-ID: <20050407130933.1578873113.durai@isofttech.com> (raw)
In-Reply-To: <20050407125744.588722761.durai@isofttech.com>
Hi,
I forgot to tell you that We are running 2.4.18 linux kernel in a
big endian mips platform. Has it been already tested in some of the big end=
ian platforms?
regards
durai
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-04-07 7:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-02 8:45 [Bluez-devel] support for CSR Bluecore4 chip durai
2005-04-03 19:00 ` Marcel Holtmann
2005-04-07 7:27 ` durai
2005-04-07 7:39 ` durai [this message]
2005-04-07 10:10 ` Marcel Holtmann
2005-04-07 10:08 ` 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=20050407130933.1578873113.durai@isofttech.com \
--to=durai@isofttech.com \
--cc=bluez-devel@lists.sourceforge.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox