From: "Michel Dänzer" <michdaen@iiic.ethz.ch>
To: Till Straumann <Till.Straumann@TU-Berlin.de>
Cc: linuxppc-dev@lists.linuxppc.org, linux-irda@pasta.cs.uit.no
Subject: Re: IRDA/IRCOMM on a TiBook patch
Date: 19 Oct 2001 16:10:42 +0200 [thread overview]
Message-ID: <1003500642.4732.451.camel@pismo> (raw)
In-Reply-To: <3BCFCA2C.CACD571B@TU-Berlin.de>
On Fri, 2001-10-19 at 08:37, Till Straumann wrote:
>
> Michel Dänzer wrote:
> >
> > On Tue, 2001-10-16 at 12:47, Till Straumann wrote:
> >
> > > I (and I believe other people as well) had problems
> > > setting up IRDA/IRCOMM on a TiBook / 2.4.12-benh and
> > > older 2.4 series kernels [on powerpc].
> > >
> > > As far as I could find out there are several problems:
> > >
> > > 1) There seems to be a timing problem when opening
> > > the irda port which prevents it from being properly
> > > initialized.
> > >
> > > When I run "irattach /dev/ttyS1 -s 1", my Nokia 8890
> > > is never discovered. However, when I issue a 'cat /dev/ttyS1',
> > > prior to starting irattach (i.e. by opening the device
> > > [and holding it open until irattach starts]),
> > > things are properly initialized
> > > and discovery works. Putting 'mdelay(100);' somewhere
> > > in macserial.c:rs_open() does the job. However, I have
> > > not yet figured out what exactly causes the problem.
> > > A user space work-around involves patching irattach.c
> > >
> > > 2) There is an endianness bug. A possible solution is attached.
> >
> > Your patch seems to be missing a bit (in qos.c IIRC) though.
>
> What is it missing? Please, be a little bit more verbose :-)
The same thing you're doing for the other files, i.e. replace param->pv.b
by param->pv.b.ll and param->pv.s by param->pv.s.l . The build fails for
that file otherwise.
I'm talking about net/irda/qos.c BTW.
> > > 3) When applying 1) and 2), IRCOMM works provided that
> > > /proc/sys/net/irda/max_baud_rate is clamped to 57600.
> > > Apparently, there is another problem in 'macserial.c' where speeds
> > > higher than 57600 are treated especially.
> >
> > Have you managed to do anything 'real' yet? I tried your patch, and it
> > does seem to improve things, irdadump seems to show data from my Palm,
> > but I haven't succeeded to synchronize yet.
> >
>
> Sure - I can open a modem connection to my cellphone and issue any AT
> command I want. However, I have to take care of all of the three issues
> mentioned. (I.e. use patched irattach, use patched kernel and
> echo 57600 > /proc/sys/net/irda/max_baud_rate).
I have done the latter two and used cat to work around the first. I see
something with irdadump but none of the pilot sync tools work. I'm
afraid they're broken on PPC yet. :(
--
Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer
XFree86 and DRI project member / CS student, Free Software enthusiast
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-10-19 14:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-16 10:47 IRDA/IRCOMM on a TiBook patch Till Straumann
2001-10-19 1:02 ` Michel Dänzer
2001-10-19 6:37 ` Till Straumann
2001-10-19 14:10 ` Michel Dänzer [this message]
2001-10-19 17:24 ` IRDA/IRCOMM on a TiBook patch (UPDATED) Till Straumann
2001-10-20 1:13 ` Michel Dänzer
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=1003500642.4732.451.camel@pismo \
--to=michdaen@iiic.ethz.ch \
--cc=Till.Straumann@TU-Berlin.de \
--cc=linux-irda@pasta.cs.uit.no \
--cc=linuxppc-dev@lists.linuxppc.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.