From: Pavel Machek <pavel@ucw.cz>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: bluez-devel@lists.sourceforge.net,
kernel list <linux-kernel@vger.kernel.org>
Subject: Re: Problems with CF bluetooth
Date: Thu, 29 Sep 2005 23:32:19 +0200 [thread overview]
Message-ID: <20050929213219.GA2180@elf.ucw.cz> (raw)
In-Reply-To: <1128016693.6052.2.camel@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 1909 bytes --]
Hi!
> > I believe it would happen with any other CF card, too. Can you
> > hciattach it, unplug, hciattach again?
>
> actually I don't have any of them with me and I don't saw a problem with
> my Casira of a serial port.
Following patch seems to work around it. And yes, printk() triggers
twice after
root@amd:~# ~pavel/bin/billionton_start
hciattach: no process killed
hci0: Type: UART
BD Address: 00:10:60:AB:25:9A ACL MTU: 192:8 SCO MTU: 64:8
UP RUNNING PSCAN ISCAN
RX bytes:201 acl:0 sco:0 events:9 errors:0
TX bytes:168 acl:0 sco:0 commands:8 errors:0
root@amd:~# ~pavel/bin/billionton_start
no state->info
no state->info
hci0: Type: UART
BD Address: 00:10:60:AB:25:9A ACL MTU: 192:8 SCO MTU: 64:8
UP RUNNING PSCAN ISCAN
RX bytes:201 acl:0 sco:0 events:9 errors:0
TX bytes:168 acl:0 sco:0 commands:8 errors:0
root@amd:~#
Pavel
Workaround billionton eject problem.
---
commit 81a2889a21eb2bfdf8b242f2cc2cc1d6ad424ea2
tree 35187ac07854fda50f07e9de3eb1c46db2cdd0a7
parent 5fb2493e110ff081e4463e7ab65eff487a3a14f6
author <pavel@amd.(none)> Thu, 29 Sep 2005 23:21:18 +0200
committer <pavel@amd.(none)> Thu, 29 Sep 2005 23:21:18 +0200
drivers/serial/serial_core.c | 4 +++-
1 files changed, 3 insertions(+), 1 deletions(-)
diff --git a/drivers/serial/serial_core.c b/drivers/serial/serial_core.c
--- a/drivers/serial/serial_core.c
+++ b/drivers/serial/serial_core.c
@@ -521,7 +521,9 @@ static void uart_flush_buffer(struct tty
DPRINTK("uart_flush_buffer(%d) called\n", tty->index);
spin_lock_irqsave(&port->lock, flags);
- uart_circ_clear(&state->info->xmit);
+ if (!state->info)
+ printk(KERN_CRIT "no state->info\n");
+ else uart_circ_clear(&state->info->xmit);
spin_unlock_irqrestore(&port->lock, flags);
tty_wakeup(tty);
}
--
if you have sharp zaurus hardware you don't need... you know my address
[-- Attachment #2: billionton_start --]
[-- Type: text/plain, Size: 260 bytes --]
# Take 2.6.12-rc3-mm3
#
# PCMCIA config:
# card "Cyber-blue Compact Flash Card"
# manfid 0x0279, 0x950b
# bind "serial_cs"
#
killall hciattach
sleep .1
setserial /dev/ttyBT baud_base 921600
hciattach -s 921600 /dev/ttyBT bcsp
hciconfig hci0 up
hciconfig
next prev parent reply other threads:[~2005-09-29 21:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-29 13:48 Problems with CF bluetooth Pavel Machek
2005-09-29 13:56 ` [Bluez-devel] " Nelson Murilo
2005-09-29 15:45 ` Marcel Holtmann
2005-09-29 15:56 ` Pavel Machek
2005-09-29 16:29 ` Marcel Holtmann
2005-09-29 17:54 ` Pavel Machek
2005-09-29 17:58 ` Marcel Holtmann
2005-09-29 21:32 ` Pavel Machek [this message]
2005-09-29 21:37 ` Russell King
2005-09-29 21:43 ` Pavel Machek
2005-09-29 21:45 ` Russell King
2005-09-29 21:52 ` Pavel Machek
2005-09-29 22:01 ` Russell King
2005-09-29 22:04 ` Pavel Machek
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=20050929213219.GA2180@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=bluez-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--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.