Re: [d-i] Testing daily image of d-i
On di, 2006-12-05 at 17:24 +0100, Michael Schmitz wrote:
> > > > These are for 2.6.19, but with minor changes (re-adding the pt_regs * argument
> > > > to interrupt routines), it should apply to 2.6.18.
> > > Yes, those are basically the patches that are in Ingo's 2.6.14 kernel.
> > If you want me to test the kernel (2.6.18) with your patches applied, you'll
> > need to make them for me... ;)
> > Currently Spice is down, so this would be a good moment to install a new
> > kernel. ;)
> I've prepared a patch that should apply cleanly on top of 2.6.18-5 (the
> current Debian kernel source for m68k).
There are some strange things to your patch...
--- ../linux-2.6-2.6.18-debian/debian/build/build-m68k-none-amiga/arch/m68k/configs/amiga_defconfig 2006-09-20 05:42:06.000000000 +0200
+++ arch/m68k/configs/amiga_defconfig 2006-12-05 16:41:35.000000000 +0100
@@ -249,7 +249,9 @@
Strange, the CONFIG_SCSI_NCR53C7xx_FAST symbol gets added to
amiga_defconfig, bvme6000_defconfig and mvme16x_defconfig but it got
--- ../linux-2.6-2.6.18-debian/debian/build/build-m68k-none-amiga/drivers/scsi/Kconfig 2006-11-24 16:11:09.000000000 +0100
+++ drivers/scsi/Kconfig 2006-12-05 16:41:35.000000000 +0100
@@ -1801,17 +1793,9 @@
SCSI controller chip. Almost everyone using one of these boards
will want to say Y to this question.
- bool "allow FAST-SCSI [10MHz]"
- depends on SCSI_AMIGA7XX || MVME16x_SCSI || BVME6000_SCSI
- This will enable 10MHz FAST-SCSI transfers with your host
- adapter. Some systems have problems with that speed, so it's safest
- to say N here.
tristate "Sun3 NCR5380 SCSI"
depends on SUN3 && SCSI
This option will enable support for the OBIO (onboard io) NCR5380
Plus, your patch re-adds some headers which are no longer needed:
drivers/scsi/amiga7xx.h, drivers/scsi/bvme6000.h and
drivers/scsi/mvme16x.h (apparently already removed in
--- ../linux-2.6-2.6.18-debian/debian/build/build-m68k-none-amiga/include/asm-m68k/io.h 2006-11-24 16:11:09.000000000 +0100
+++ include/asm-m68k/io.h 2006-12-05 16:41:27.000000000 +0100
is not from me. Is this a 2.6.19 fix? Or from EtherNEC?