From: jason@openinformatics.com (Jason E. Stewart)
To: linuxppc-dev@lists.linuxppc.org, debian-powerpc@lists.debian.org
Subject: Re: IrDA-patched binaries
Date: 12 Nov 2001 09:39:01 -0700 [thread overview]
Message-ID: <87vggg2bbu.fsf@openinformatics.com> (raw)
In-Reply-To: <3BEF9DA6.14AF8E49@iiic.ethz.ch>
"Michel Dänzer" <michdaen@iiic.ethz.ch> writes:
> "Jason E. Stewart" wrote:
> >
> > "Jonas Smedegaard" <dr@jones.dk> writes:
> >
> > > I have made available kernel and irda-packages with the irda-hacks
> > > added to make .
> >
> > I was totally thrilled to see this. Because of reiserfs, I need to
> > compile my own kernel, so I grabbed the patches a couple of weeks
> > ago. I just had time to look at them and it seems that parameters.h
> > has changed a *lot* since this patch was made.
> >
> > >From BenH's latest kernel:
> >
> > typedef union {
> > char *c;
> > __u32 i;
> > __u32 *ip;
> > } irda_pv_t;
>
> Yup, 2.4.15-pre2 has my better fix. :)
sorry Michel, I don't understand. Is the irda_pv_t listed above your
fix? Or will your fix being showing up in BenH's kernel soon, or???
> Now we're working on fixing macserial such that the 'cat /dev/ttyS1
> trick' isn't needed anymore...
Hmmm.. Sorry, must have missed that one. What is the trick, and why is
it needed?
Thanks,
jas.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-11-12 16:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-01 22:24 IrDA-patched binaries Jonas Smedegaard
2001-11-01 22:30 ` [Debian] " Jonas Smedegaard
2001-11-11 23:10 ` Jason E. Stewart
2001-11-12 9:52 ` Jonas Smedegaard
2001-11-12 10:00 ` Michel Dänzer
2001-11-12 10:39 ` Jonas Smedegaard
2001-11-12 16:39 ` Jason E. Stewart [this message]
2001-11-12 20:47 ` Michel Dänzer
2001-11-12 21:16 ` Jason E. Stewart
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=87vggg2bbu.fsf@openinformatics.com \
--to=jason@openinformatics.com \
--cc=debian-powerpc@lists.debian.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).