Re: New per subarch 2.4.22 powerpc kernels, please test.

[Sven Luther <sven.luther@wanadoo.fr>]

On Mon, Oct 06, 2003 at 02:18:33PM +0200, Hubert Figuiere wrote:
> On Mon, 2003-10-06 at 13:38, Sven Luther wrote:
> 
> >  
> > > Last time I tried miboot.image build myself it did not boot. I'll try
> > > this one later this week to let you know.
> 
> I just wanted to add that this was with benH tree grabbed from BK.
> 
> > > 
> > > My biggest problem is AHA2930B (SCSI controller) support in the kernel
> > > that seemed to be missing from any pre-build package I found beside
> > > 2.2.20....
> > > 
> > > AHA2930B is the only reason I use miboot instead of quik.
> > 
> > Mmm, The aic7xxx_old.c driver does have a line : 
> > 
> >   PCI_VENDOR_ID_ADAPTEC2, PCI_DEVICE_ID_ADAPTEC2_2930U2, AHC_AIC7890,
> > 
> > But i suppose this is not the same (2930U2 instead of 2930B).
> 
> Here is the PCI info (/proc/pci from 2.2.20)
> 
>   Bus  0, device  17, function  0:
>     SCSI storage controller: Adaptec AIC-7860 (rev 1).
>       Medium devsel.  Fast back-to-back capable.  IRQ 30.  Master
> Capable.  Latency=32.  Min Gnt=4.Max Lat=4.
>       I/O at 0x0 [0x1].
>       Non-prefetchable 32 bit memory at 0x80800000 [0x80800000].
> 
> OF device is:
> bandit/ADPT,2930BU
> and it is not OF bootable :-( hence, no quik.
> 
> It seems to be in the aic7xxx driver.

This may be the one : 

    "Adaptec AIC-7860 Ultra SCSI host adapter",           /* AIC_7860 */

> Each time I tried to boot with miBoot from a pre-build 2.4 kernel it did
> not find the adapter. Each I try to boot a kernel I build, (using
> image.miboot, or zImage), miBoot just fails.

The kernel entries that correspond are :

CONFIG_SCSI_AIC7XXX=m
CONFIG_AIC7XXX_CMDS_PER_DEVICE=8
CONFIG_AIC7XXX_RESET_DELAY_MS=15000
# CONFIG_AIC7XXX_PROBE_EISA_VL is not set
# CONFIG_AIC7XXX_BUILD_FIRMWARE is not set
# CONFIG_AIC7XXX_DEBUG_ENABLE is not set
CONFIG_AIC7XXX_DEBUG_MASK=0
# CONFIG_AIC7XXX_REG_PRETTY_PRINT is not set
CONFIG_SCSI_AIC79XX=m

And for the aic7xxx_old : 

CONFIG_SCSI_AIC7XXX_OLD=m

So, both are built as modules, and since we have to use a 3 floppy set
for miboot anyway, it should be ok to use them :

First flopyy  : minimal kernel
Second floppy : minimal root image, with floppy drivers.
Third floppy  : rest of the drivers, maybe more than one floppy.

So there may be support for this in the future.

Friendly,

Sven Luther