[parisc-linux] HP/UX 10.20 800 series media?

[parisc-linux] HP/UX 10.20 800 series media?

[Matthew Hudson]

I know this is off topic, but I just aquired a k200
and I'd like to know where to get the HP/UX 10.20
install media. I have an 8 user license, I just need
the media.

Now on subject. K200 working in Linux and if so
is there SMP support yet?

-Matt

Re: [parisc-linux] HP/UX 10.20 800 series media?

[Matthew Wilcox]

On Mon, Jul 24, 2000 at 11:53:06AM -0500, Matthew Hudson wrote:
> Now on subject. K200 working in Linux and if so
> is there SMP support yet?

we're not really interested in supporting the k class right now.
it's pretty similar to early C/J class (C100, C110, J200, J210), but it
has some `interesting' devices in it that may be hard to support (the
SCSI adapter looks slightly strange).  we don't have any SMP support yet
and this machine won't be high on the priority list when we do start
working on SMP.  i guess you're going to have to join in and do some
hacking yourself :-)

-- 
Revolutions do not require corporate support.

[parisc-linux] HIL hardware Qs

[Brian S. Julin]

OK, well this weekend I finally started working on a linux-input 
style driver for the HIL.  Unfortunately, I'm working with nothing
but other people's source and bare metal... I asked earlier
and noone came up with any substantial docs on the HIL.

So far the OpenBSD HIL driver has been the most helpful source.
While the linux driver does the wiser thing and does all the
key cooking in software, it's really just a basic bootstrap 
driver.  The BSD driver is prepared to deal with other devices 
on the HIL bus.

I'm trying to get a good abstraction of the HIL from the devices
on it as per the linux-input model (HIL ports -> struct serio and HIL
devices- > struct input)

My questions revolve around a comment at the polloff/pollon
functions in the BSD driver and the true nature of the relationship
between the 8042 and the HIL.  

/*
 * Send a command to a device on the loop.
 * Since only one command can be active on the loop at any time,
 * we must ensure that we are not interrupted during this process.
 * Hence we mask interrupts to prevent potential access from most
 * interrupt routines and turn off auto-polling to disable the
 * internally generated poll commands.
 */

The code then proceeds to tell the 8042 to stop polling.  I thought
the 8042 was basically just an adaptor to accomodate the PS/2-style
keyboards and mice.  But when I turn off the 8042 polling, I no 
longer get any interrupts even from my HIL keyboard.  So I guess the
8042 here is an integral part of the HIL.

Turning off/on polling as they suggest would cause a tangle as far
as clean abstraction between the HIL and the devices on it.  Not
insurmountable, but not something to be writing if I don't absolutley
have to.

So the first question is... were the BSD guys being completely
paranoid, or do we really have to worry about internally generated
commands on the loop?  If so, is there a better way to safeguard this.
Third, if I have to abandon using the IRQ and just poll from a timer,
do we have all the timer_list guts yet, or is that area incomplete?

Finally, can anyone explain the HIL_68K intricacy and what's going on
there? 

Anyone with better docs or source on hand than what I have, please
do send them.

BTW, I won't even really be able to compile this code until we do another
merge with the mainstream source, because the linux-input/linux-console
project keeps their CVS pretty bleeding edge, so don't expect anything 
functional too very soon.

--
Brian S. Julin

[parisc-linux] The Kxx0 machines and other questions.

[Matthew Hudson]

> On Mon, Jul 24, 2000 at 11:53:06AM -0500, Matthew Hudson wrote:
> > Now on subject. K200 working in Linux and if so
> > is there SMP support yet?
> 
> we're not really interested in supporting the k class right now.
> it's pretty similar to early C/J class (C100, C110, J200, J210), but it
> has some `interesting' devices in it that may be hard to support (the
> SCSI adapter looks slightly strange).  we don't have any SMP support yet
> and this machine won't be high on the priority list when we do start
> working on SMP.  i guess you're going to have to join in and do some
> hacking yourself :-)

Like I have the time for this, but... (famous last words)

Since I haven't had the time (yet) to attempt booting into Linux
with this monster what is its status? Non-functional or?
Where can I get some documentation for the various hardware in
this machine.

What is the status of the J210XC and will I be able to create
a functional Linux environment for it(the J210) if I wanted to
start coding? (currently running 10.20)

-Matt

Re: [parisc-linux] The Kxx0 machines and other questions.

[Grant Grundler]

Matthew Hudson wrote:
> Mathew Wilcox (?) wrote:
> > we're not really interested in supporting the k class right now.
> > it's pretty similar to early C/J class (C100, C110, J200, J210), but it
> > has some `interesting' devices in it that may be hard to support (the
> > SCSI adapter looks slightly strange).  we don't have any SMP support yet
> > and this machine won't be high on the priority list when we do start
> > working on SMP.  i guess you're going to have to join in and do some
> > hacking yourself :-)
> 
> Like I have the time for this, but... (famous last words)
> 
> Since I haven't had the time (yet) to attempt booting into Linux
> with this monster what is its status? Non-functional or?
> Where can I get some documentation for the various hardware in
> this machine.

Non-functional since U2/Uturn code is not ready yet (I'm working on it)
and not documented (let's not go there again right now). And even
if it were ready, I need to hack in some sort of an "I/O tree"
in order to support more than one U2/Uturn. K-class can have
multiple U2/Uturns.

The core I/O board has a NCR 53c720 chip with zalon - Richard Hirst
is working on that already. AFIAK, Zalon isn't documented but it's trivial
to initialize and the real problem is support for c720 chip in linux.

AFAICT, Built-in LAN, PS/2, serial ports, and SE SCSI are off a LASI.
Same chip as what's documented for the A180/712/et al.
But the firmware might be reporting them differently...someone who
cares will have to figure this out.

I doubt documents or code for the gecko-boa (GSC to HP-PB bus converter)
will ever get published....and even if it did, getting docs for the HP-PB
(aka NIO) devices is another huge hurdle. Look for a "HARRIER"
(card carrier for K-class, provides 4 "gsc" "slots") if you don't already
have one. At least some of the GSC devices (like tachyon, c720) will
get or are supported already.

> What is the status of the J210XC and will I be able to create
> a functional Linux environment for it(the J210) if I wanted to
> start coding? (currently running 10.20)

Once the U2/Uturn support is in place and user space stabilizes, yes.

Audio and graphics continue to be a problem WRT documentation and code.
I don't know what's up with "WAX" (EISA) support.

Matt, I didn't see a J210XC in the HW database.
(http://www.thepuffingroup.com/parisc/hw.html)
Since you asked about status and I've written this detailed reply,
I'd consider you a real dork at this point if you didn't enter
the J210XC into the HW database.  Could you please?
(thanks in advance :^)

grant

Grant Grundler
Unix Development Lab
+1.408.447.7253

Re: [parisc-linux] The Kxx0 machines and other questions.

[Matthew Hudson]

> 
> Matt, I didn't see a J210XC in the HW database.
> (http://www.thepuffingroup.com/parisc/hw.html)
> Since you asked about status and I've written this detailed reply,
> I'd consider you a real dork at this point if you didn't enter
> the J210XC into the HW database.  Could you please?
> (thanks in advance :^)

I will as soon as I figure out how. ;-)

-Matt