From: Christian Gennerat <xgen@free.fr>
To: Dumitru Ciobarcianu <Dumitru.Ciobarcianu@iNES.RO>
Cc: jt@hpl.hp.com, James McKenzie <james@fishsoup.dhs.org>,
Christian Gennerat <christian.gennerat@polytechnique.org>,
Martin Lucina <mato@kotelna.sk>,
Marcelo Tosatti <marcelo@conectiva.com.br>,
Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2.4] : donauboe IrDA driver (resend)
Date: Fri, 20 Dec 2002 19:05:08 +0100 [thread overview]
Message-ID: <3E035BD4.9000304@free.fr> (raw)
In-Reply-To: 1040381739.1084.43.camel@localhost.localdomain
As I am not on LKML, I have not seen your
http://www.uwsg.indiana.edu/hypermail/linux/kernel/0212.2/0900.html
only Jean's reply.
Your problem is the same as Martin Lucina had, and I can reply the same as
Martin Lucina a écrit:
> kern.log:Oct 25 20:06:12 localhost kernel:
> TSTST<3>toshoboeprobe(1152000) failed filter test
>
> That's an almost 50/50 failure rate, by a completely unscientific
> estimate.
> Is the self test actually neccessary for the chip to function? If not,
> is there much point in having it enabled, at least as far as 2.4.x is
> concerned?
>
>
>
The test shows that there is a deep misunderstanding of how works
MIR mode, and chaining blocks for optimization at MIR mode.
some people say "MIR works" . That is good for them.
I would prefer to have "#undef USE_MIR"
So, test is not necessary for every day use. Just put
options donauboe do_probe=0
in your /etc/modules.conf
next prev parent reply other threads:[~2002-12-20 17:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-19 2:46 [PATCH 2.4] : donauboe IrDA driver (resend) Jean Tourrilhes
2002-12-19 15:05 ` Dumitru Ciobarcianu
2002-12-19 18:56 ` Jean Tourrilhes
2002-12-20 10:55 ` Dumitru Ciobarcianu
2002-12-20 18:05 ` Christian Gennerat [this message]
2002-12-21 9:16 ` Dumitru Ciobarcianu
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=3E035BD4.9000304@free.fr \
--to=xgen@free.fr \
--cc=Dumitru.Ciobarcianu@iNES.RO \
--cc=christian.gennerat@polytechnique.org \
--cc=james@fishsoup.dhs.org \
--cc=jt@hpl.hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=mato@kotelna.sk \
/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.