From: James Bottomley <James.Bottomley@steeleye.com>
To: Richard Hirst <rhirst@linuxcare.com>
Cc: PARISC list <parisc-linux@lists.parisc-linux.org>
Subject: Re: [parisc-linux] Re: [parisc-linux-cvs] linux-2.6 willy
Date: 28 Sep 2003 12:24:26 -0500 [thread overview]
Message-ID: <1064769945.10841.1.camel@mulgrave> (raw)
In-Reply-To: <20030928165631.GS5759@sleepie.demon.co.uk>
On Sun, 2003-09-28 at 11:56, Richard Hirst wrote:
> Only because I didn't get it to work properly when I did the original
> 720 support, iirc. The chip does have INTFLY. I _think_ INTFLY worked
> a bit, but the driver tended to miss interrupts sometimes. Could easily
> have been a driver bug. Was a long time ago now though, so I could be
> misremembering.
Actually, the 720 is bust in silicon. The 770 has a properly working
intfly, but the 720's doesnt work reliably. Actually, the Q720 board
this driver also drives is wired to have a special "intfly" from a board
register to get around the problem.
James
next prev parent reply other threads:[~2003-09-28 17:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030927072449.5AF0F494058@palinux.hppa>
2003-09-28 16:56 ` [parisc-linux] Re: [parisc-linux-cvs] linux-2.6 willy Richard Hirst
2003-09-28 17:24 ` James Bottomley [this message]
2003-09-28 18:05 ` Richard Hirst
2003-09-28 19:23 ` Matthew Wilcox
2003-09-28 19:25 ` James Bottomley
[not found] <20031009140021.9199A4941DC@palinux.hppa>
2003-10-09 17:24 ` [parisc-linux] " Joel Soete
2003-10-09 17:34 ` Matthew Wilcox
2003-10-10 7:34 ` Joel Soete
[not found] <3F892DC8.30307@tiscali.be>
2003-10-13 11:34 ` [parisc-linux] " Joel Soete
[not found] <20031218143016.775DA494259@palinux.hppa>
2003-12-18 17:53 ` [parisc-linux] " Joel Soete
[not found] <20040217125236.BF8124940B2@palinux.hppa>
2004-02-17 18:16 ` Joel Soete
[not found] <20040321220309.EEF2A494553@palinux.hppa>
2004-03-23 4:52 ` [parisc-linux] " Grant Grundler
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=1064769945.10841.1.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=parisc-linux@lists.parisc-linux.org \
--cc=rhirst@linuxcare.com \
/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.