From: Ralf Baechle <ralf@linux-mips.org>
To: Stanislaw Skowronek <sskowron@ET.PUT.Poznan.PL>
Cc: Thiemo Seufer <ths@networkno.de>, linux-mips@linux-mips.org
Subject: Re: Origin 200 Status
Date: Mon, 11 Jul 2005 14:57:18 +0100 [thread overview]
Message-ID: <20050711135718.GU2765@linux-mips.org> (raw)
In-Reply-To: <Pine.GSO.4.10.10507100808410.6614-100000@helios.et.put.poznan.pl>
On Sun, Jul 10, 2005 at 08:13:56AM +0200, Stanislaw Skowronek wrote:
> > [4294678.019000] IOC3 part: [], serial: [] => class IP27 BaseIO
>
> This is not really weird, the IOC3 on the IP27 board has no NICs. We'd
> have to trace the BRIDGE NICs or even HUB NICs to get the serials, so I
> decided that it's an overkill. Although it will be required for reliably
> detecting MENET (which has a serial# NIC on the BRIDGE).
Of course there's a NIC. The driver has no special handling for IP27 and
is capable of reading the NICs on some machines at least. That would be
a rather suprising ability if there was no NIC associated with that IOC3 ;-)
(A while ago I recall a few second hand Origins were being sold on eBay
with NICs removed ...)
> > [4294678.020000] ioc3_probe : request_irq fails for IRQ 0x4
>
> This is weird. This means the keyboard will not be operational, and I wish
> somebody (Ralf) looks into this. The IOC3 on IP27 BaseIO is a dual-slot
> device (takes two IRQs, the INTA and INTA+2).
All information that I have says only INTA is being used for IP27. It
will probably take a bit of testing.
I haven't yet had any complaints about keyboard and mouse being non-
functional on IP27 - even though my Origin has 4 keyboard and 4 mouse
ports ;-)
Ralf
next prev parent reply other threads:[~2005-07-11 13:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-09 20:54 Origin 200 Status Thiemo Seufer
2005-07-10 6:13 ` Stanislaw Skowronek
2005-07-11 13:57 ` Ralf Baechle [this message]
2005-07-11 14:08 ` Stanislaw Skowronek
2005-07-11 22:35 ` Ralf Baechle
2005-07-12 7:20 ` Stanislaw Skowronek
2005-07-12 7:22 ` Ralf Baechle
2005-07-12 8:40 ` Geert Uytterhoeven
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=20050711135718.GU2765@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-mips@linux-mips.org \
--cc=sskowron@ET.PUT.Poznan.PL \
--cc=ths@networkno.de \
/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