Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: Stanislaw Skowronek <sskowron@ET.PUT.Poznan.PL>
Cc: linux-mips@linux-mips.org
Subject: Re: Origin 200 Status
Date: Mon, 11 Jul 2005 23:35:12 +0100	[thread overview]
Message-ID: <20050711223512.GA2808@linux-mips.org> (raw)
In-Reply-To: <Pine.GSO.4.10.10507111605570.23550-100000@helios.et.put.poznan.pl>

On Mon, Jul 11, 2005 at 04:08:00PM +0200, Stanislaw Skowronek wrote:

> > 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 ;-)
> 
> There is only a MAC NIC on a machine ths has. Remember that the Octane
> does not have the BaseIO NIC at the IOC3; both NICs placed there are
> actually hacks because of XBOW MicroLAN bug.

I was speaking of IP27, obviously.

> > > 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.
> 
> Yeah, change the interrupt assignments in ioc3.c, plug in a keyboard and
> try. If it works, everybody wins :)

I could do - but the plane ticket to plug the keyboard is on you ;-)

  Ralf

  reply	other threads:[~2005-07-12  7:13 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
2005-07-11 14:08     ` Stanislaw Skowronek
2005-07-11 22:35       ` Ralf Baechle [this message]
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=20050711223512.GA2808@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=linux-mips@linux-mips.org \
    --cc=sskowron@ET.PUT.Poznan.PL \
    /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