Re: 3.4-beta on B132L and E55 / PCI support

Making, drinking tea and reading an opus magnum from Jochen Kunz:
[Charset ISO-8859-1 unsupported, filtering to ASCII...]
> Hi.

re

> I am new to this list and OpenBSD. I instaled the 3.4-beta snapshot on
> my 715/100XC and it seams to run fine. The installation was a bit
> complicated. There was no lif34.fs as desribed in the installation
> instructions. lif33.fs paniced at the end auf autoconf(9). So I used an
> old 3.2 kernel with NFS root and did the disklabel / newfs / tar ... by
> hand. The 3.2 kernel spit out some errors about osiop(4) and ie(4) but I
> got the 3.4-beta snapshot onto the disk. 

it is on the ftp.usa . i suggest you contact the mirror maintainer
you have downloaded the snapshot from.

> BTW: Why did the kernel use the old Sun rarp/bootparamd method? Even the
> boot ROM in the 715/100XC supported dhcp/bootp. 

you are confused.
bootp/tftp is used by the prom to load the kernel.
rarpd/bootparam are used to configure root on nfs
(should you have chosen that one).

> Today I connected the disk from the 715/100XC to a B132L and it just
> booted to multi user. (Serial console) I noticed that it says:
> "WAX Bus Adapter" at phantomas0 (type b, sv 8e) offset fe00000 not
> configured
> "PCI Bridge" at phantomas0 (type d, sv a) offset ff80000 not configured
> AFAIK WAX is the EISA bridge and the PCI bridge is the Dino chip. 
> Is anyone working on an EISA and more interresting on a PCI attachment?
> I have done some hacking on NetBSD/powerpc (PReP and CHRP) that included
> PCI attachments. I am willing to work on the Dino / PCI support. But,
> obviously, I don't want to duplicate work someone else is already doing.

this code should come after 3.4 is out as it did not
make it on time for 3.4 w/ support in dc(4) and siop(4).

> I tried to boot the 3.4-beta snapshot on an E55 too. 
> All I got was: [see dmesg below]
> So it seams that this machine is not supported in any way?
> Again: I am willing to do some work on the support for this machine. It
> looks like it paniced somewhere in the pmap(9) module and I am not aware
> of uvm(9) / pmap(9) internas. So this may exceed my current skills. But
> if someone else supplies a kernel I will throw it at may hardware. 

it is not listed as supported and thus is not supported.
i'd say support for those machines is kinda low-priority
since they contain those funky hp-pb modules that we
most likely will never support anyway.

cu

-- 
    paranoic mickey       (my employers have changed but, the name has remained)