From: Jonathan Bredin <jbredin@coloradocollege.edu>
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] Re: creating the bnep0 device
Date: Mon, 28 Mar 2005 13:52:15 -0700 [thread overview]
Message-ID: <42486E7F.8050407@coloradocollege.edu> (raw)
Thanks, Anderson and Marcel.
I think that I must have been too slow in moving between the two
devices.... bnep0 comes up at both sites, now.
At the slave side, though, I get
NETDEV WATCHDOG: bnep0: transmit timed out
once I try to use the connection. I'll dig around and see if can figure
it out.
Thanks!
jonathan
-------------------------------------------------------
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-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next reply other threads:[~2005-03-28 20:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-28 20:52 Jonathan Bredin [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-03-28 20:00 [Bluez-users] Re: creating the bnep0 device Jonathan Bredin
2005-03-28 20:05 ` 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=42486E7F.8050407@coloradocollege.edu \
--to=jbredin@coloradocollege.edu \
--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