From: "Choi Sonim" <choisonim@gmail.com>
To: "BlueZ development" <bluez-devel@lists.sourceforge.net>,
"Marcel Holtmann" <marcel@holtmann.org>
Subject: Re: [Bluez-devel] loading of hci_uart.ko
Date: Mon, 29 Jan 2007 11:57:00 +0200 [thread overview]
Message-ID: <4f436aae0701290157h3ac80220t801fffccdc2b8a8c@mail.gmail.com> (raw)
In-Reply-To: <1169235297.29458.19.camel@violet>
Hi Marcel,
On 1/19/07, Marcel Holtmann <marcel@holtmann.org> wrote:
> > when I do "hciattach /dev/ttyS0 any", somehow the needed module
> > hci_uart.ko is loaded.
> > I looked in hciattach.c but I do not see how is it done ?
>
> # modinfo hci_uart
> alias: tty-ldisc-15
>
> It tells the kernel to load this module if any application request the
> line discipline 15.
can you please elaborate on this ? when the app request the HCI line
discipline, how does the kernel knows it need to look for alias tty-ldisc-15 ?
does it then run modprobe ?
what code is responsible for that ?
thank you very much for the help
choi
>
> Regards
>
> Marcel
>
>
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Bluez-devel mailing list
> Bluez-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-devel
>
next prev parent reply other threads:[~2007-01-29 9:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-19 19:04 [Bluez-devel] loading of hci_uart.ko Choi Sonim
2007-01-19 19:34 ` Marcel Holtmann
2007-01-29 9:57 ` Choi Sonim [this message]
2007-01-29 10:05 ` Marcel Holtmann
2007-01-29 10:42 ` Choi Sonim
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=4f436aae0701290157h3ac80220t801fffccdc2b8a8c@mail.gmail.com \
--to=choisonim@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox