On Wed, Jan 01, 2003 at 02:20:12PM +0100, Hendrik Scholz wrote:

> - custom kernel/your kernel with adaptec support and
(various combinations)
>    => "timedout scb" problem

> - custom kernel w/o ahc support but with symbios support:
>   - same combinations, always the same problems

Weird.  Weird.  Weird.

>   - netbooting works and shows the prompt where I should select the
>     root device. I didn't manage to use nfs root with the mec0
>     interface. My tlp0 (plugged in the pci slot) cannot be used for
>     nfs root as it didn't get an ip.

Er, right.  mec support doesn't exist.  Here's how to netboot an ip32:

* drop a supported NIC (I've tested rtk, ne, and ex -- I think Rafal tested
  an fxp somewhere along the line) into the PCI slot,
* connect both the mec and the PCI NIC to the network,
* configure your bootserver's dhcpd.conf thusly:

  subnet 192.168.11.0 netmask 255.255.255.0 {
        host erwin {
                hardware ethernet 00:90:99:7f:94:5d;
                fixed-address 192.168.11.9;
                option root-path "/usr/local/exports/erwin";
                server-name="192.168.11.4";
        }
        host erwin-mec {
                hardware ethernet 08:00:69:0c:a0:93;
                fixed-address 192.168.11.9;
                option root-path "/usr/local/exports/erwin";
                server-name="192.168.11.4";
        }

  ... replacing the server-name value with the bootserver IP, root-path with
  the path to the NFS root, and so forth.

* boot from mec using the bootp() semantics.
* feed the root: prompt the PCI NIC name.

That's how I bootstrapped my ip32.

> Is the mec0 interface supported or is it just a stub?

See above.  I sussed out the register mapping, but I can _never_ get DMA right,
and the mec isn't a PIO device :(

-- Chris
	GPG key FEB9DE7F (91AF 4534 4529 4BCC 31A5  938E 023E EEFB FEB9 DE7F)