public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: pokui@ucu.ac.ug
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] travelmate c110
Date: Mon, 18 Oct 2004 16:42:01 +0300 (EAT)	[thread overview]
Message-ID: <34204.81.199.88.27.1098106921.squirrel@ucu.ac.ug> (raw)

Hi all,

The chipset on my acer travelmate c110 doesn't seem to be supported
because typing "hcitool dev" gives me:
Devices:
#

1. Is there anyway I can tell what chipset this laptop is using (and
cross-check against the h/w list).

2. Given that the chipset may not be supported (if I can find out what the
answer to 1 is), what would I need to add support for this chipset (in
terms of what major parts of the code do I need to modify etc)

thanks.


-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

             reply	other threads:[~2004-10-18 13:42 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-18 13:42 pokui [this message]
2004-10-18 13:48 ` [Bluez-users] travelmate c110 Marcel Holtmann
2004-10-18 13:54   ` pokui
2004-10-18 14:19     ` Marcel Holtmann
2004-10-19 13:08       ` pokui
2004-10-19 13:16         ` Marcel Holtmann
2004-10-19 13:21           ` pokui
2004-10-19 14:12             ` pokui
2004-10-19 14:26               ` pokui
2004-10-19 14:54                 ` Marcel Holtmann
2004-10-19 10:42   ` [Bluez-users] Student query: a question about multihop libo
2004-10-19 10:56     ` 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=34204.81.199.88.27.1098106921.squirrel@ucu.ac.ug \
    --to=pokui@ucu.ac.ug \
    --cc=bluez-users@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