* Linux-2.6.9-rc2 kernel build for mvme5100
@ 2004-09-16 4:29 David Gardiner
2004-09-16 5:36 ` Matt Porter
0 siblings, 1 reply; 12+ messages in thread
From: David Gardiner @ 2004-09-16 4:29 UTC (permalink / raw)
To: linuxppc-dev
[-- Attachment #1: Type: text/plain, Size: 3034 bytes --]
Hi all,
I've got two questions in regard to building linux-2.6.9-rc2 for a mvme5100
Target info:
build platform: mvme5100, gcc-3.3.4, debian-testing, linuxppc_2_4_devel,
default mvme5100 config
target platform: mvme5100
Questions 1:
I was getting this error when I tried to build the kernel:
CC arch/ppc/boot/common/bootinfo.o
CC arch/ppc/boot/common/misc-common.o
CC arch/ppc/boot/common/ns16550.o
arch/ppc/boot/common/ns16550.c:14: error: conflicting types for `outb'
include/asm/io.h:142: error: previous declaration of `outb'
arch/ppc/boot/common/ns16550.c:15: error: conflicting types for `inb'
include/asm/io.h:157: error: previous declaration of `inb'
make[2]: *** [arch/ppc/boot/common/ns16550.o] Error 1
make[1]: *** [arch/ppc/boot/common] Error 2
make: *** [zImage] Error 2
I changed arch/ppc/boot/common/ns16550.c so that it managed to compile
based on what was in io.h, the patch for which is attatched, are these
changes okay?
Question 2:
I'm now getting the error:
daveg@occy:/usr/src/play-2.6.9.new$ make
CHK include/linux/version.h
make[1]: `arch/ppc/kernel/asm-offsets.s' is up to date.
CHK include/linux/compile.h
GZIP arch/ppc/boot/images/vmlinux.gz
HOSTCC arch/ppc/boot/utils/addnote
HOSTCC arch/ppc/boot/utils/mknote
HOSTCC arch/ppc/boot/utils/hack-coff
HOSTCC arch/ppc/boot/utils/mkprep
HOSTCC arch/ppc/boot/utils/mkbugboot
HOSTCC arch/ppc/boot/utils/mktree
AS arch/ppc/boot/simple/head.o
AS arch/ppc/boot/simple/relocate.o
CC arch/ppc/boot/simple/misc.o
CC arch/ppc/boot/simple/dummy.o
objcopy -O elf32-powerpc \
--add-section=.image=arch/ppc/boot/images/vmlinux.gz \
--set-section-flags=.image=contents,alloc,load,readonly,data \
arch/ppc/boot/simple/dummy.o arch/ppc/boot/simple/image.o
ld -T /usr/src/play-2.6.9.new/arch/ppc/boot/ld.script -Ttext 0x00800000
-Bstatic -o arch/ppc/boot/simple/zvmlinux arch/ppc/boot/simple/head.o
arch/ppc/boot/simple/relocate.o arch/ppc/boot/simple/misc.o
arch/ppc/boot/simple/image.o arch/ppc/boot/common/lib.a
arch/ppc/boot/lib/lib.a
arch/ppc/boot/common/lib.a(ns16550.o)(.text+0x2e): In function
`serial_init':
: undefined reference to `isa_io_base'
arch/ppc/boot/common/lib.a(ns16550.o)(.text+0x42): In function
`serial_init':
: undefined reference to `isa_io_base'
arch/ppc/boot/common/lib.a(ns16550.o)(.text+0x7e): In function
`serial_init':
: undefined reference to `isa_io_base'
arch/ppc/boot/common/lib.a(ns16550.o)(.text+0x86): In function
`serial_init':
: undefined reference to `isa_io_base'
arch/ppc/boot/common/lib.a(ns16550.o)(.text+0xda): In function
`serial_init':
: undefined reference to `isa_io_base'
arch/ppc/boot/common/lib.a(ns16550.o)(.text+0xfa): more undefined
references to `isa_io_base' follow
make[2]: *** [arch/ppc/boot/simple/zvmlinux] Error 1
make[1]: *** [simple] Error 2
make: *** [zImage] Error 2
Now I know isa_io_base is declared/defined in arch/ppc/kernel/pci.c so
how is it supposed to link?
Ta,
dlg
[-- Attachment #2: ns16550.c.patch --]
[-- Type: text/plain, Size: 1880 bytes --]
--- linux/arch/ppc/boot/common/ns16550.c 2004-08-14 20:56:23.000000000 +1000
+++ play-2.6.9.new/arch/ppc/boot/common/ns16550.c 2004-09-16 13:56:44.000000000 +1000
@@ -11,8 +11,8 @@
#define SERIAL_BAUD 9600
-extern void outb(int port, unsigned char val);
-extern unsigned char inb(int port);
+extern void outb(unsigned int val, unsigned int port);
+extern unsigned int inb(unsigned int port);
extern unsigned long ISA_io;
static struct serial_state rs_table[RS_TABLE_SIZE] = {
@@ -47,7 +47,7 @@
/* save the LCR */
lcr = inb(com_port + (UART_LCR << shift));
/* Access baud rate */
- outb(com_port + (UART_LCR << shift), 0x80);
+ outb(0x80, com_port + (UART_LCR << shift));
dlm = inb(com_port + (UART_DLM << shift));
/*
* Test if serial port is unconfigured.
@@ -58,20 +58,20 @@
if ((dlm <= 4) && (lcr & 2))
/* port is configured, put the old LCR back */
- outb(com_port + (UART_LCR << shift), lcr);
+ outb(lcr, com_port + (UART_LCR << shift));
else {
/* Input clock. */
- outb(com_port + (UART_DLL << shift),
- (BASE_BAUD / SERIAL_BAUD) & 0xFF);
- outb(com_port + (UART_DLM << shift),
- (BASE_BAUD / SERIAL_BAUD) >> 8);
+ outb((BASE_BAUD / SERIAL_BAUD) & 0xFF,
+ com_port + (UART_DLL << shift));
+ outb((BASE_BAUD / SERIAL_BAUD) >> 8,
+ com_port + (UART_DLM << shift));
/* 8 data, 1 stop, no parity */
- outb(com_port + (UART_LCR << shift), 0x03);
+ outb(0x03, com_port + (UART_LCR << shift));
/* RTS/DTR */
- outb(com_port + (UART_MCR << shift), 0x03);
+ outb(0x03, com_port + (UART_MCR << shift));
}
/* Clear & enable FIFOs */
- outb(com_port + (UART_FCR << shift), 0x07);
+ outb(0x07, com_port + (UART_FCR << shift));
return (com_port);
}
@@ -81,7 +81,7 @@
{
while ((inb(com_port + (UART_LSR << shift)) & UART_LSR_THRE) == 0)
;
- outb(com_port, c);
+ outb(c, com_port);
}
unsigned char
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Linux-2.6.9-rc2 kernel build for mvme5100
2004-09-16 4:29 Linux-2.6.9-rc2 kernel build for mvme5100 David Gardiner
@ 2004-09-16 5:36 ` Matt Porter
2004-09-16 7:54 ` David Gardiner
0 siblings, 1 reply; 12+ messages in thread
From: Matt Porter @ 2004-09-16 5:36 UTC (permalink / raw)
To: David Gardiner; +Cc: linuxppc-dev
On Thu, Sep 16, 2004 at 02:29:49PM +1000, David Gardiner wrote:
> Hi all,
>
> I've got two questions in regard to building linux-2.6.9-rc2 for a mvme5100
>
> Target info:
> build platform: mvme5100, gcc-3.3.4, debian-testing, linuxppc_2_4_devel,
> default mvme5100 config
> target platform: mvme5100
>
> Questions 1:
>
> I was getting this error when I tried to build the kernel:
>
> CC arch/ppc/boot/common/bootinfo.o
> CC arch/ppc/boot/common/misc-common.o
> CC arch/ppc/boot/common/ns16550.o
> arch/ppc/boot/common/ns16550.c:14: error: conflicting types for `outb'
> include/asm/io.h:142: error: previous declaration of `outb'
> arch/ppc/boot/common/ns16550.c:15: error: conflicting types for `inb'
> include/asm/io.h:157: error: previous declaration of `inb'
> make[2]: *** [arch/ppc/boot/common/ns16550.o] Error 1
> make[1]: *** [arch/ppc/boot/common] Error 2
> make: *** [zImage] Error 2
>
> I changed arch/ppc/boot/common/ns16550.c so that it managed to compile
> based on what was in io.h, the patch for which is attatched, are these
> changes okay?
You need this patch:
http://www.ussg.iu.edu/hypermail/linux/kernel/0409.1/1192.html
-Matt
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Linux-2.6.9-rc2 kernel build for mvme5100
2004-09-16 5:36 ` Matt Porter
@ 2004-09-16 7:54 ` David Gardiner
2004-09-20 17:32 ` Tom Rini
0 siblings, 1 reply; 12+ messages in thread
From: David Gardiner @ 2004-09-16 7:54 UTC (permalink / raw)
To: Matt Porter; +Cc: linuxppc-dev
>You need this patch:
> http://www.ussg.iu.edu/hypermail/linux/kernel/0409.1/1192.html
>
>-Matt
>
>
Thanks that compiles, but it doesn't boot, I got:
Network Boot File load in progress... To abort hit <BREAK>
Bytes Received =&1305095, Bytes Loaded =&1305095
Bytes/Second =&1305095, Elapsed Time =1 Second(s)
Residual-Data Located at: $1FEA137C
loaded at: 00005400 00144530
relocated to: 00800000 0093F130
zimage at: 00805905 0093CA9F
avail ram: 00400000 00800000
Linux/PPC load: ip=on panic=3 bigphysarea=8192 root=/dev/sda5
Uncompressing Linux...done.
Now booting the kernel
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Linux-2.6.9-rc2 kernel build for mvme5100
2004-09-16 7:54 ` David Gardiner
@ 2004-09-20 17:32 ` Tom Rini
2004-09-20 19:23 ` Matt Porter
0 siblings, 1 reply; 12+ messages in thread
From: Tom Rini @ 2004-09-20 17:32 UTC (permalink / raw)
To: David Gardiner; +Cc: linuxppc-dev
On Thu, Sep 16, 2004 at 05:54:08PM +1000, David Gardiner wrote:
>
> >You need this patch:
> >http://www.ussg.iu.edu/hypermail/linux/kernel/0409.1/1192.html
> >
> >-Matt
> >
> >
> Thanks that compiles, but it doesn't boot, I got:
Did you disable CONFIG_VT, if it was enabled? Otherwise you need to
pass console=ttyS0
--
Tom Rini
http://gate.crashing.org/~trini/
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Linux-2.6.9-rc2 kernel build for mvme5100
2004-09-20 17:32 ` Tom Rini
@ 2004-09-20 19:23 ` Matt Porter
2004-09-20 22:55 ` David Gardiner
2004-09-21 9:15 ` Marius Groeger
0 siblings, 2 replies; 12+ messages in thread
From: Matt Porter @ 2004-09-20 19:23 UTC (permalink / raw)
To: Tom Rini; +Cc: linuxppc-dev
On Mon, Sep 20, 2004 at 10:32:41AM -0700, Tom Rini wrote:
> On Thu, Sep 16, 2004 at 05:54:08PM +1000, David Gardiner wrote:
>
> >
> > >You need this patch:
> > >http://www.ussg.iu.edu/hypermail/linux/kernel/0409.1/1192.html
> > >
> > >-Matt
> > >
> > >
> > Thanks that compiles, but it doesn't boot, I got:
>
> Did you disable CONFIG_VT, if it was enabled? Otherwise you need to
> pass console=ttyS0
and on recent kernels, you need console=ttyS0,9600 on boards like
this that use 9600 baud. Baud rate used to default to 9600, but
no longer.
-Matt
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Linux-2.6.9-rc2 kernel build for mvme5100
2004-09-20 19:23 ` Matt Porter
@ 2004-09-20 22:55 ` David Gardiner
2004-09-21 0:12 ` David Gardiner
2004-09-22 16:33 ` Tom Rini
2004-09-21 9:15 ` Marius Groeger
1 sibling, 2 replies; 12+ messages in thread
From: David Gardiner @ 2004-09-20 22:55 UTC (permalink / raw)
To: Matt Porter; +Cc: linuxppc-dev
[-- Attachment #1: Type: text/plain, Size: 1265 bytes --]
>>>>You need this patch:
>>>>http://www.ussg.iu.edu/hypermail/linux/kernel/0409.1/1192.html
>>>>
>>>>-Matt
>>>>
>>>>
Okay I took a different way, looking at the code and having lots of
problems trying to get it to compile and the similarity between the
PowerPlus series I compiled a pplus kernel with the default config and
the patch above and it booted, yeah, and dumped bits to the console, on
an mvme2604.
So I made some changes Kconfig so that MVME5100 and PPLUS were basically
the same ( The architecture for the 5100 and pplus are similar, so why
was the code separated? arrgh I'm about to be burnt to a crisp, but if
we don't get our fingers burnt we never learn) which the patch for is
attached. This patch also allows the selection of nvram which I want
also and it seems to compile no matter what you select, which it didn't
before. And so selecting MVME5100 it booted and dumped bits to the
console, yeah.
I'm still playing with the config, so please excuse the "weird"
selections in the config which is also attached, but the notable
differences between it and the arch/ppc/configs/mvme5100_defconfig are
that it has selections for a default console, and input devices ( which
isn't needed, I know) and .....
Ta,
dlg
[-- Attachment #2: 2.6.9-rc2-w-patch.patch --]
[-- Type: text/plain, Size: 728 bytes --]
diff -burN play-2.6.9.patched/arch/ppc/Kconfig play-2.6.9.patched.changed/arch/ppc/Kconfig
--- play-2.6.9.patched/arch/ppc/Kconfig 2004-09-20 11:56:00.000000000 +1000
+++ play-2.6.9.patched.changed/arch/ppc/Kconfig 2004-09-20 12:40:11.000000000 +1000
@@ -686,7 +686,7 @@
config PPC_GEN550
bool
depends on SANDPOINT || MCPN765 || SPRUCE || PPLUS || PCORE || \
- PRPMC750 || K2 || PRPMC800 || LOPEC
+ PRPMC750 || K2 || PRPMC800 || LOPEC || MVME5100
default y
config FORCE
@@ -763,7 +763,7 @@
default "115200"
config PPCBUG_NVRAM
- bool "Enable reading PPCBUG NVRAM during boot" if PPLUS || LOPEC
+ bool "Enable reading PPCBUG NVRAM during boot" if PPLUS || LOPEC || MVME5100
default y if PPC_PREP
config SMP
[-- Attachment #3: config.mvme5100.works --]
[-- Type: text/plain, Size: 15856 bytes --]
#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.8.1
# Tue Sep 21 07:48:45 2004
#
CONFIG_MMU=y
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_HAVE_DEC_LOCK=y
CONFIG_PPC=y
CONFIG_PPC32=y
CONFIG_GENERIC_NVRAM=y
#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y
CONFIG_CLEAN_COMPILE=y
CONFIG_BROKEN_ON_SMP=y
#
# General setup
#
CONFIG_LOCALVERSION=""
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
# CONFIG_POSIX_MQUEUE is not set
# CONFIG_BSD_PROCESS_ACCT is not set
CONFIG_SYSCTL=y
# CONFIG_AUDIT is not set
CONFIG_LOG_BUF_SHIFT=14
CONFIG_HOTPLUG=y
CONFIG_IKCONFIG=y
CONFIG_IKCONFIG_PROC=y
CONFIG_EMBEDDED=y
CONFIG_KALLSYMS=y
# CONFIG_KALLSYMS_EXTRA_PASS is not set
CONFIG_FUTEX=y
CONFIG_EPOLL=y
CONFIG_IOSCHED_NOOP=y
CONFIG_IOSCHED_AS=y
CONFIG_IOSCHED_DEADLINE=y
CONFIG_IOSCHED_CFQ=y
# CONFIG_CC_OPTIMIZE_FOR_SIZE is not set
CONFIG_SHMEM=y
# CONFIG_TINY_SHMEM is not set
#
# Loadable module support
#
CONFIG_MODULES=y
CONFIG_MODULE_UNLOAD=y
# CONFIG_MODULE_FORCE_UNLOAD is not set
CONFIG_OBSOLETE_MODPARM=y
# CONFIG_MODVERSIONS is not set
CONFIG_KMOD=y
#
# Processor
#
CONFIG_6xx=y
# CONFIG_40x is not set
# CONFIG_44x is not set
# CONFIG_POWER3 is not set
# CONFIG_POWER4 is not set
# CONFIG_8xx is not set
# CONFIG_E500 is not set
# CONFIG_ALTIVEC is not set
# CONFIG_TAU is not set
# CONFIG_CPU_FREQ is not set
CONFIG_PPC_GEN550=y
CONFIG_PPC_STD_MMU=y
#
# Platform options
#
# CONFIG_PPC_MULTIPLATFORM is not set
# CONFIG_APUS is not set
# CONFIG_WILLOW is not set
# CONFIG_PCORE is not set
# CONFIG_POWERPMC250 is not set
# CONFIG_EV64260 is not set
# CONFIG_SPRUCE is not set
# CONFIG_LOPEC is not set
# CONFIG_MCPN765 is not set
CONFIG_MVME5100=y
# CONFIG_PPLUS is not set
# CONFIG_PRPMC750 is not set
# CONFIG_PRPMC800 is not set
# CONFIG_SANDPOINT is not set
# CONFIG_ADIR is not set
# CONFIG_K2 is not set
# CONFIG_PAL4 is not set
# CONFIG_GEMINI is not set
# CONFIG_EST8260 is not set
# CONFIG_SBC82xx is not set
# CONFIG_SBS8260 is not set
# CONFIG_RPX8260 is not set
# CONFIG_TQM8260 is not set
# CONFIG_ADS8272 is not set
# CONFIG_LITE5200 is not set
# CONFIG_MVME5100_IPMC761_PRESENT is not set
CONFIG_PPCBUG_NVRAM=y
# CONFIG_SMP is not set
CONFIG_PREEMPT=y
CONFIG_HIGHMEM=y
CONFIG_BINFMT_ELF=y
CONFIG_BINFMT_MISC=y
CONFIG_CMDLINE_BOOL=y
CONFIG_CMDLINE="root=/dev/hde1 panic=10 bigphysarea=8192"
#
# Bus options
#
CONFIG_GENERIC_ISA_DMA=y
CONFIG_PCI=y
CONFIG_PCI_DOMAINS=y
CONFIG_PCI_LEGACY_PROC=y
CONFIG_PCI_NAMES=y
#
# PCMCIA/CardBus support
#
# CONFIG_PCMCIA is not set
#
# Advanced setup
#
# CONFIG_ADVANCED_OPTIONS is not set
#
# Default settings for advanced configuration options are used
#
CONFIG_HIGHMEM_START=0xfe000000
CONFIG_LOWMEM_SIZE=0x30000000
CONFIG_KERNEL_START=0xc0000000
CONFIG_TASK_SIZE=0x80000000
CONFIG_BOOT_LOAD=0x00800000
#
# Device Drivers
#
#
# Generic Driver Options
#
CONFIG_STANDALONE=y
CONFIG_PREVENT_FIRMWARE_BUILD=y
# CONFIG_FW_LOADER is not set
#
# Memory Technology Devices (MTD)
#
# CONFIG_MTD is not set
#
# Parallel port support
#
# CONFIG_PARPORT is not set
#
# Plug and Play support
#
#
# Block devices
#
CONFIG_BLK_DEV_FD=y
# CONFIG_BLK_CPQ_DA is not set
# CONFIG_BLK_CPQ_CISS_DA is not set
# CONFIG_BLK_DEV_DAC960 is not set
# CONFIG_BLK_DEV_UMEM is not set
# CONFIG_BLK_DEV_LOOP is not set
# CONFIG_BLK_DEV_NBD is not set
# CONFIG_BLK_DEV_SX8 is not set
# CONFIG_BLK_DEV_RAM is not set
# CONFIG_LBD is not set
#
# ATA/ATAPI/MFM/RLL support
#
CONFIG_IDE=y
CONFIG_BLK_DEV_IDE=y
#
# Please see Documentation/ide.txt for help/info on IDE drives
#
# CONFIG_BLK_DEV_IDE_SATA is not set
CONFIG_BLK_DEV_IDEDISK=y
CONFIG_IDEDISK_MULTI_MODE=y
# CONFIG_BLK_DEV_IDECD is not set
# CONFIG_BLK_DEV_IDETAPE is not set
# CONFIG_BLK_DEV_IDEFLOPPY is not set
CONFIG_BLK_DEV_IDESCSI=y
# CONFIG_IDE_TASK_IOCTL is not set
# CONFIG_IDE_TASKFILE_IO is not set
#
# IDE chipset support/bugfixes
#
CONFIG_IDE_GENERIC=y
CONFIG_BLK_DEV_IDEPCI=y
# CONFIG_IDEPCI_SHARE_IRQ is not set
# CONFIG_BLK_DEV_OFFBOARD is not set
# CONFIG_BLK_DEV_GENERIC is not set
# CONFIG_BLK_DEV_OPTI621 is not set
# CONFIG_BLK_DEV_SL82C105 is not set
CONFIG_BLK_DEV_IDEDMA_PCI=y
# CONFIG_BLK_DEV_IDEDMA_FORCED is not set
# CONFIG_IDEDMA_PCI_AUTO is not set
CONFIG_BLK_DEV_ADMA=y
# CONFIG_BLK_DEV_AEC62XX is not set
# CONFIG_BLK_DEV_ALI15X3 is not set
# CONFIG_BLK_DEV_AMD74XX is not set
# CONFIG_BLK_DEV_CMD64X is not set
# CONFIG_BLK_DEV_TRIFLEX is not set
# CONFIG_BLK_DEV_CY82C693 is not set
# CONFIG_BLK_DEV_CS5520 is not set
# CONFIG_BLK_DEV_CS5530 is not set
# CONFIG_BLK_DEV_HPT34X is not set
# CONFIG_BLK_DEV_HPT366 is not set
# CONFIG_BLK_DEV_SC1200 is not set
# CONFIG_BLK_DEV_PIIX is not set
# CONFIG_BLK_DEV_NS87415 is not set
# CONFIG_BLK_DEV_PDC202XX_OLD is not set
CONFIG_BLK_DEV_PDC202XX_NEW=y
CONFIG_PDC202XX_FORCE=y
# CONFIG_BLK_DEV_SVWKS is not set
# CONFIG_BLK_DEV_SIIMAGE is not set
# CONFIG_BLK_DEV_SLC90E66 is not set
# CONFIG_BLK_DEV_TRM290 is not set
# CONFIG_BLK_DEV_VIA82CXXX is not set
# CONFIG_IDE_ARM is not set
CONFIG_BLK_DEV_IDEDMA=y
# CONFIG_IDEDMA_IVB is not set
# CONFIG_IDEDMA_AUTO is not set
# CONFIG_BLK_DEV_HD is not set
#
# SCSI device support
#
CONFIG_SCSI=y
CONFIG_SCSI_PROC_FS=y
#
# SCSI support type (disk, tape, CD-ROM)
#
CONFIG_BLK_DEV_SD=y
CONFIG_CHR_DEV_ST=y
# CONFIG_CHR_DEV_OSST is not set
CONFIG_BLK_DEV_SR=y
CONFIG_BLK_DEV_SR_VENDOR=y
CONFIG_CHR_DEV_SG=y
#
# Some SCSI devices (e.g. CD jukebox) support multiple LUNs
#
# CONFIG_SCSI_MULTI_LUN is not set
CONFIG_SCSI_CONSTANTS=y
# CONFIG_SCSI_LOGGING is not set
#
# SCSI Transport Attributes
#
# CONFIG_SCSI_SPI_ATTRS is not set
# CONFIG_SCSI_FC_ATTRS is not set
#
# SCSI low-level drivers
#
# CONFIG_BLK_DEV_3W_XXXX_RAID is not set
# CONFIG_SCSI_3W_9XXX is not set
# CONFIG_SCSI_ACARD is not set
# CONFIG_SCSI_AACRAID is not set
# CONFIG_SCSI_AIC7XXX is not set
# CONFIG_SCSI_AIC7XXX_OLD is not set
# CONFIG_SCSI_AIC79XX is not set
# CONFIG_SCSI_DPT_I2O is not set
# CONFIG_MEGARAID_NEWGEN is not set
# CONFIG_MEGARAID_LEGACY is not set
# CONFIG_SCSI_SATA is not set
# CONFIG_SCSI_BUSLOGIC is not set
# CONFIG_SCSI_DMX3191D is not set
# CONFIG_SCSI_EATA is not set
# CONFIG_SCSI_EATA_PIO is not set
# CONFIG_SCSI_FUTURE_DOMAIN is not set
# CONFIG_SCSI_GDTH is not set
# CONFIG_SCSI_IPS is not set
# CONFIG_SCSI_INIA100 is not set
# CONFIG_SCSI_SYM53C8XX_2 is not set
# CONFIG_SCSI_IPR is not set
# CONFIG_SCSI_QLOGIC_ISP is not set
# CONFIG_SCSI_QLOGIC_FC is not set
# CONFIG_SCSI_QLOGIC_1280 is not set
CONFIG_SCSI_QLA2XXX=y
# CONFIG_SCSI_QLA21XX is not set
# CONFIG_SCSI_QLA22XX is not set
# CONFIG_SCSI_QLA2300 is not set
# CONFIG_SCSI_QLA2322 is not set
# CONFIG_SCSI_QLA6312 is not set
# CONFIG_SCSI_QLA6322 is not set
# CONFIG_SCSI_DC395x is not set
# CONFIG_SCSI_DC390T is not set
# CONFIG_SCSI_NSP32 is not set
# CONFIG_SCSI_DEBUG is not set
#
# Multi-device support (RAID and LVM)
#
# CONFIG_MD is not set
#
# Fusion MPT device support
#
# CONFIG_FUSION is not set
#
# IEEE 1394 (FireWire) support
#
# CONFIG_IEEE1394 is not set
#
# I2O device support
#
# CONFIG_I2O is not set
#
# Macintosh device drivers
#
#
# Networking support
#
CONFIG_NET=y
#
# Networking options
#
CONFIG_PACKET=y
# CONFIG_PACKET_MMAP is not set
# CONFIG_NETLINK_DEV is not set
CONFIG_UNIX=y
# CONFIG_NET_KEY is not set
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
# CONFIG_IP_ADVANCED_ROUTER is not set
# CONFIG_IP_PNP is not set
# CONFIG_NET_IPIP is not set
# CONFIG_NET_IPGRE is not set
# CONFIG_IP_MROUTE is not set
# CONFIG_ARPD is not set
CONFIG_SYN_COOKIES=y
# CONFIG_INET_AH is not set
# CONFIG_INET_ESP is not set
# CONFIG_INET_IPCOMP is not set
# CONFIG_INET_TUNNEL is not set
#
# IP: Virtual Server Configuration
#
# CONFIG_IP_VS is not set
# CONFIG_IPV6 is not set
CONFIG_NETFILTER=y
# CONFIG_NETFILTER_DEBUG is not set
#
# IP: Netfilter Configuration
#
CONFIG_IP_NF_CONNTRACK=m
# CONFIG_IP_NF_CT_ACCT is not set
# CONFIG_IP_NF_CT_PROTO_SCTP is not set
CONFIG_IP_NF_FTP=m
# CONFIG_IP_NF_IRC is not set
# CONFIG_IP_NF_TFTP is not set
# CONFIG_IP_NF_AMANDA is not set
# CONFIG_IP_NF_QUEUE is not set
CONFIG_IP_NF_IPTABLES=m
CONFIG_IP_NF_MATCH_LIMIT=m
# CONFIG_IP_NF_MATCH_IPRANGE is not set
CONFIG_IP_NF_MATCH_MAC=m
CONFIG_IP_NF_MATCH_PKTTYPE=m
CONFIG_IP_NF_MATCH_MARK=m
CONFIG_IP_NF_MATCH_MULTIPORT=m
CONFIG_IP_NF_MATCH_TOS=m
# CONFIG_IP_NF_MATCH_RECENT is not set
CONFIG_IP_NF_MATCH_ECN=m
CONFIG_IP_NF_MATCH_DSCP=m
CONFIG_IP_NF_MATCH_AH_ESP=m
# CONFIG_IP_NF_MATCH_LENGTH is not set
# CONFIG_IP_NF_MATCH_TTL is not set
# CONFIG_IP_NF_MATCH_TCPMSS is not set
CONFIG_IP_NF_MATCH_HELPER=m
CONFIG_IP_NF_MATCH_STATE=m
CONFIG_IP_NF_MATCH_CONNTRACK=m
CONFIG_IP_NF_MATCH_OWNER=m
# CONFIG_IP_NF_MATCH_ADDRTYPE is not set
# CONFIG_IP_NF_MATCH_REALM is not set
# CONFIG_IP_NF_MATCH_SCTP is not set
CONFIG_IP_NF_FILTER=m
CONFIG_IP_NF_TARGET_REJECT=m
# CONFIG_IP_NF_TARGET_LOG is not set
CONFIG_IP_NF_TARGET_ULOG=m
# CONFIG_IP_NF_TARGET_TCPMSS is not set
CONFIG_IP_NF_NAT=m
CONFIG_IP_NF_NAT_NEEDED=y
CONFIG_IP_NF_TARGET_MASQUERADE=m
CONFIG_IP_NF_TARGET_REDIRECT=m
# CONFIG_IP_NF_TARGET_NETMAP is not set
# CONFIG_IP_NF_TARGET_SAME is not set
# CONFIG_IP_NF_NAT_LOCAL is not set
# CONFIG_IP_NF_NAT_SNMP_BASIC is not set
CONFIG_IP_NF_NAT_FTP=m
# CONFIG_IP_NF_MANGLE is not set
# CONFIG_IP_NF_RAW is not set
CONFIG_IP_NF_ARPTABLES=m
CONFIG_IP_NF_ARPFILTER=m
# CONFIG_IP_NF_ARP_MANGLE is not set
CONFIG_IP_NF_COMPAT_IPCHAINS=m
# CONFIG_IP_NF_COMPAT_IPFWADM is not set
#
# SCTP Configuration (EXPERIMENTAL)
#
# CONFIG_IP_SCTP is not set
# CONFIG_ATM is not set
# CONFIG_BRIDGE is not set
# CONFIG_VLAN_8021Q is not set
# CONFIG_DECNET is not set
# CONFIG_LLC2 is not set
# CONFIG_IPX is not set
# CONFIG_ATALK is not set
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
# CONFIG_NET_DIVERT is not set
# CONFIG_ECONET is not set
# CONFIG_WAN_ROUTER is not set
# CONFIG_NET_HW_FLOWCONTROL is not set
#
# QoS and/or fair queueing
#
# CONFIG_NET_SCHED is not set
# CONFIG_NET_CLS_ROUTE is not set
#
# Network testing
#
# CONFIG_NET_PKTGEN is not set
# CONFIG_NETPOLL is not set
# CONFIG_NET_POLL_CONTROLLER is not set
# CONFIG_HAMRADIO is not set
# CONFIG_IRDA is not set
# CONFIG_BT is not set
CONFIG_NETDEVICES=y
# CONFIG_DUMMY is not set
# CONFIG_BONDING is not set
# CONFIG_EQUALIZER is not set
# CONFIG_TUN is not set
#
# ARCnet devices
#
# CONFIG_ARCNET is not set
#
# Ethernet (10 or 100Mbit)
#
CONFIG_NET_ETHERNET=y
CONFIG_MII=y
# CONFIG_HAPPYMEAL is not set
# CONFIG_SUNGEM is not set
# CONFIG_NET_VENDOR_3COM is not set
#
# Tulip family network device support
#
CONFIG_NET_TULIP=y
# CONFIG_DE2104X is not set
CONFIG_TULIP=y
# CONFIG_TULIP_MWI is not set
# CONFIG_TULIP_MMIO is not set
# CONFIG_TULIP_NAPI is not set
# CONFIG_DE4X5 is not set
# CONFIG_WINBOND_840 is not set
# CONFIG_DM9102 is not set
# CONFIG_HP100 is not set
CONFIG_NET_PCI=y
# CONFIG_PCNET32 is not set
# CONFIG_AMD8111_ETH is not set
# CONFIG_ADAPTEC_STARFIRE is not set
# CONFIG_B44 is not set
# CONFIG_FORCEDETH is not set
# CONFIG_DGRS is not set
CONFIG_EEPRO100=y
# CONFIG_EEPRO100_PIO is not set
# CONFIG_E100 is not set
# CONFIG_FEALNX is not set
# CONFIG_NATSEMI is not set
# CONFIG_NE2K_PCI is not set
# CONFIG_8139CP is not set
# CONFIG_8139TOO is not set
# CONFIG_SIS900 is not set
# CONFIG_EPIC100 is not set
# CONFIG_SUNDANCE is not set
# CONFIG_TLAN is not set
# CONFIG_VIA_RHINE is not set
# CONFIG_VIA_VELOCITY is not set
#
# Ethernet (1000 Mbit)
#
# CONFIG_ACENIC is not set
# CONFIG_DL2K is not set
# CONFIG_E1000 is not set
# CONFIG_NS83820 is not set
# CONFIG_HAMACHI is not set
# CONFIG_YELLOWFIN is not set
# CONFIG_R8169 is not set
# CONFIG_SK98LIN is not set
# CONFIG_TIGON3 is not set
#
# Ethernet (10000 Mbit)
#
# CONFIG_IXGB is not set
# CONFIG_S2IO is not set
#
# Token Ring devices
#
# CONFIG_TR is not set
#
# Wireless LAN (non-hamradio)
#
# CONFIG_NET_RADIO is not set
#
# Wan interfaces
#
# CONFIG_WAN is not set
# CONFIG_FDDI is not set
# CONFIG_HIPPI is not set
# CONFIG_PPP is not set
# CONFIG_SLIP is not set
# CONFIG_NET_FC is not set
# CONFIG_SHAPER is not set
# CONFIG_NETCONSOLE is not set
#
# ISDN subsystem
#
# CONFIG_ISDN is not set
#
# Telephony Support
#
# CONFIG_PHONE is not set
#
# Input device support
#
# CONFIG_INPUT is not set
#
# Userland interfaces
#
#
# Input I/O drivers
#
# CONFIG_GAMEPORT is not set
CONFIG_SOUND_GAMEPORT=y
# CONFIG_SERIO is not set
# CONFIG_SERIO_I8042 is not set
#
# Input Device Drivers
#
#
# Character devices
#
# CONFIG_VT is not set
# CONFIG_SERIAL_NONSTANDARD is not set
#
# Serial drivers
#
CONFIG_SERIAL_8250=y
CONFIG_SERIAL_8250_CONSOLE=y
CONFIG_SERIAL_8250_NR_UARTS=4
# CONFIG_SERIAL_8250_EXTENDED is not set
#
# Non-8250 serial port support
#
CONFIG_SERIAL_CORE=y
CONFIG_SERIAL_CORE_CONSOLE=y
CONFIG_UNIX98_PTYS=y
CONFIG_LEGACY_PTYS=y
CONFIG_LEGACY_PTY_COUNT=256
#
# IPMI
#
# CONFIG_IPMI_HANDLER is not set
#
# Watchdog Cards
#
# CONFIG_WATCHDOG is not set
# CONFIG_NVRAM is not set
CONFIG_GEN_RTC=y
# CONFIG_GEN_RTC_X is not set
# CONFIG_DTLK is not set
# CONFIG_R3964 is not set
# CONFIG_APPLICOM is not set
#
# Ftape, the floppy tape device driver
#
# CONFIG_AGP is not set
# CONFIG_DRM is not set
# CONFIG_RAW_DRIVER is not set
#
# I2C support
#
# CONFIG_I2C is not set
#
# Dallas's 1-wire bus
#
# CONFIG_W1 is not set
#
# Misc devices
#
#
# Multimedia devices
#
# CONFIG_VIDEO_DEV is not set
#
# Digital Video Broadcasting Devices
#
# CONFIG_DVB is not set
#
# Graphics support
#
# CONFIG_FB is not set
#
# Sound
#
# CONFIG_SOUND is not set
#
# USB support
#
# CONFIG_USB is not set
#
# USB Gadget Support
#
# CONFIG_USB_GADGET is not set
#
# File systems
#
CONFIG_EXT2_FS=y
# CONFIG_EXT2_FS_XATTR is not set
CONFIG_EXT3_FS=y
CONFIG_EXT3_FS_XATTR=y
# CONFIG_EXT3_FS_POSIX_ACL is not set
# CONFIG_EXT3_FS_SECURITY is not set
CONFIG_JBD=y
# CONFIG_JBD_DEBUG is not set
CONFIG_FS_MBCACHE=y
# CONFIG_REISERFS_FS is not set
# CONFIG_JFS_FS is not set
# CONFIG_XFS_FS is not set
# CONFIG_MINIX_FS is not set
# CONFIG_ROMFS_FS is not set
# CONFIG_QUOTA is not set
# CONFIG_AUTOFS_FS is not set
# CONFIG_AUTOFS4_FS is not set
#
# CD-ROM/DVD Filesystems
#
# CONFIG_ISO9660_FS is not set
# CONFIG_UDF_FS is not set
#
# DOS/FAT/NT Filesystems
#
# CONFIG_MSDOS_FS is not set
# CONFIG_VFAT_FS is not set
# CONFIG_NTFS_FS is not set
#
# Pseudo filesystems
#
CONFIG_PROC_FS=y
CONFIG_PROC_KCORE=y
CONFIG_SYSFS=y
CONFIG_DEVFS_FS=y
CONFIG_DEVFS_MOUNT=y
# CONFIG_DEVFS_DEBUG is not set
# CONFIG_DEVPTS_FS_XATTR is not set
# CONFIG_TMPFS is not set
# CONFIG_HUGETLB_PAGE is not set
CONFIG_RAMFS=y
#
# Miscellaneous filesystems
#
# CONFIG_ADFS_FS is not set
# CONFIG_AFFS_FS is not set
# CONFIG_HFS_FS is not set
# CONFIG_HFSPLUS_FS is not set
# CONFIG_BEFS_FS is not set
# CONFIG_BFS_FS is not set
# CONFIG_EFS_FS is not set
# CONFIG_CRAMFS is not set
# CONFIG_VXFS_FS is not set
# CONFIG_HPFS_FS is not set
# CONFIG_QNX4FS_FS is not set
# CONFIG_SYSV_FS is not set
# CONFIG_UFS_FS is not set
#
# Network File Systems
#
CONFIG_NFS_FS=y
CONFIG_NFS_V3=y
# CONFIG_NFS_V4 is not set
# CONFIG_NFS_DIRECTIO is not set
CONFIG_NFSD=y
CONFIG_NFSD_V3=y
# CONFIG_NFSD_V4 is not set
CONFIG_NFSD_TCP=y
CONFIG_LOCKD=y
CONFIG_LOCKD_V4=y
CONFIG_EXPORTFS=y
CONFIG_SUNRPC=y
# CONFIG_RPCSEC_GSS_KRB5 is not set
# CONFIG_RPCSEC_GSS_SPKM3 is not set
# CONFIG_SMB_FS is not set
# CONFIG_CIFS is not set
# CONFIG_NCP_FS is not set
# CONFIG_CODA_FS is not set
# CONFIG_AFS_FS is not set
#
# Partition Types
#
# CONFIG_PARTITION_ADVANCED is not set
CONFIG_MSDOS_PARTITION=y
#
# Native Language Support
#
# CONFIG_NLS is not set
#
# Library routines
#
# CONFIG_CRC_CCITT is not set
CONFIG_CRC32=y
# CONFIG_LIBCRC32C is not set
#
# Profiling support
#
# CONFIG_PROFILING is not set
#
# Kernel hacking
#
# CONFIG_DEBUG_KERNEL is not set
CONFIG_SERIAL_TEXT_DEBUG=y
#
# Security options
#
# CONFIG_SECURITY is not set
#
# Cryptographic options
#
# CONFIG_CRYPTO is not set
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Linux-2.6.9-rc2 kernel build for mvme5100
2004-09-20 22:55 ` David Gardiner
@ 2004-09-21 0:12 ` David Gardiner
2004-09-22 16:33 ` Tom Rini
1 sibling, 0 replies; 12+ messages in thread
From: David Gardiner @ 2004-09-21 0:12 UTC (permalink / raw)
To: linuxppc-dev
> I'm still playing with the config, so please excuse the "weird"
> selections in the config which is also attached, but the notable
> differences between it and the arch/ppc/configs/mvme5100_defconfig are
> that it has selections for a default console, and input devices (
> which isn't needed, I know) and .....
>
That should of been, the config (changed from the pplus config) I
attatched has none of the CONSOLE ... bits selected but has
CONFIG_SERIAL_TEXT_DEBUG which you need the patch I attached
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Linux-2.6.9-rc2 kernel build for mvme5100
2004-09-20 19:23 ` Matt Porter
2004-09-20 22:55 ` David Gardiner
@ 2004-09-21 9:15 ` Marius Groeger
2004-09-21 15:48 ` Tom Rini
1 sibling, 1 reply; 12+ messages in thread
From: Marius Groeger @ 2004-09-21 9:15 UTC (permalink / raw)
To: Matt Porter; +Cc: linuxppc-dev
On Mon, 20 Sep 2004, Matt Porter wrote:
>> Did you disable CONFIG_VT, if it was enabled? Otherwise you need to
>> pass console=ttyS0
>
> and on recent kernels, you need console=ttyS0,9600 on boards like
> this that use 9600 baud. Baud rate used to default to 9600, but
> no longer.
So what IS the default then? Until today, I thought you don't necessarily
need a console= argument at all. See Documentation/serial-console.txt:
If no console device is specified, the first device found capable of
acting as a system console will be used. At this time, the system first
looks for a VGA card and then for a serial port. So if you don't have a
VGA card in your system the first serial port will automatically become
the console.
Are you saying that you should always pass console=...?
Regards,
Marius
--
Marius Groeger <mgroeger@sysgo.com>
SYSGO AG Embedded and Real-Time Software
Voice: +49 6136 9948 0 FAX: +49 6136 9948 10
www.sysgo.com | www.elinos.com | www.osek.de | www.imerva.com
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Linux-2.6.9-rc2 kernel build for mvme5100
2004-09-21 9:15 ` Marius Groeger
@ 2004-09-21 15:48 ` Tom Rini
0 siblings, 0 replies; 12+ messages in thread
From: Tom Rini @ 2004-09-21 15:48 UTC (permalink / raw)
To: Marius Groeger; +Cc: linuxppc-dev
On Tue, Sep 21, 2004 at 11:15:20AM +0200, Marius Groeger wrote:
> On Mon, 20 Sep 2004, Matt Porter wrote:
> >>Did you disable CONFIG_VT, if it was enabled? Otherwise you need to
> >>pass console=ttyS0
> >
> >and on recent kernels, you need console=ttyS0,9600 on boards like
> >this that use 9600 baud. Baud rate used to default to 9600, but
> >no longer.
>
> So what IS the default then? Until today, I thought you don't necessarily
> need a console= argument at all. See Documentation/serial-console.txt:
>
> If no console device is specified, the first device found capable of
> acting as a system console will be used. At this time, the system first
> looks for a VGA card and then for a serial port. So if you don't have a
> VGA card in your system the first serial port will automatically become
> the console.
>
> Are you saying that you should always pass console=...?
Double checking my facts here, it's not CONFIG_VT per-se, but
CONFIG_VT_CONSOLE. The problem is that VT_CONSOLE will register before
anything else, even if no video hardware is found. Now getting a bit
simplistic, if you don't want VT_CONSOLE, you don't want VT, so...
--
Tom Rini
http://gate.crashing.org/~trini/
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Linux-2.6.9-rc2 kernel build for mvme5100
2004-09-20 22:55 ` David Gardiner
2004-09-21 0:12 ` David Gardiner
@ 2004-09-22 16:33 ` Tom Rini
2004-09-22 16:47 ` Matt Porter
2004-09-23 20:14 ` David Gardiner
1 sibling, 2 replies; 12+ messages in thread
From: Tom Rini @ 2004-09-22 16:33 UTC (permalink / raw)
To: David Gardiner; +Cc: linuxppc-dev
On Tue, Sep 21, 2004 at 08:55:41AM +1000, David Gardiner wrote:
> Okay I took a different way, looking at the code and having lots of
> problems trying to get it to compile and the similarity between the
> PowerPlus series I compiled a pplus kernel with the default config and
> the patch above and it booted, yeah, and dumped bits to the console, on
> an mvme2604.
>
> So I made some changes Kconfig so that MVME5100 and PPLUS were basically
> the same ( The architecture for the 5100 and pplus are similar, so why
> was the code separated? arrgh I'm about to be burnt to a crisp, but if
> we don't get our fingers burnt we never learn) which the patch for is
> attached. This patch also allows the selection of nvram which I want
> also and it seems to compile no matter what you select, which it didn't
> before. And so selecting MVME5100 it booted and dumped bits to the
> console, yeah.
I _think_ the answer is simply that the mvme5100 work predated the
CONFIG_PPLUS work. If you can come up with a patch that adds mvme5100
support to CONFIG_PPLUS, we can get rid of the MVME5100-specific stuff.
(And, if you do, please look at Documentation/SubmittingPatches and the
Developers Certificate of Origin).
> I'm still playing with the config, so please excuse the "weird"
> selections in the config which is also attached, but the notable
> differences between it and the arch/ppc/configs/mvme5100_defconfig are
> that it has selections for a default console, and input devices ( which
> isn't needed, I know) and .....
I'll try and pick out the important changes and push them up. Thanks.
--
Tom Rini
http://gate.crashing.org/~trini/
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Linux-2.6.9-rc2 kernel build for mvme5100
2004-09-22 16:33 ` Tom Rini
@ 2004-09-22 16:47 ` Matt Porter
2004-09-23 20:14 ` David Gardiner
1 sibling, 0 replies; 12+ messages in thread
From: Matt Porter @ 2004-09-22 16:47 UTC (permalink / raw)
To: Tom Rini; +Cc: linuxppc-dev
On Wed, Sep 22, 2004 at 09:33:09AM -0700, Tom Rini wrote:
> On Tue, Sep 21, 2004 at 08:55:41AM +1000, David Gardiner wrote:
>
> > Okay I took a different way, looking at the code and having lots of
> > problems trying to get it to compile and the similarity between the
> > PowerPlus series I compiled a pplus kernel with the default config and
> > the patch above and it booted, yeah, and dumped bits to the console, on
> > an mvme2604.
> >
> > So I made some changes Kconfig so that MVME5100 and PPLUS were basically
> > the same ( The architecture for the 5100 and pplus are similar, so why
> > was the code separated? arrgh I'm about to be burnt to a crisp, but if
> > we don't get our fingers burnt we never learn) which the patch for is
> > attached. This patch also allows the selection of nvram which I want
> > also and it seems to compile no matter what you select, which it didn't
> > before. And so selecting MVME5100 it booted and dumped bits to the
> > console, yeah.
>
> I _think_ the answer is simply that the mvme5100 work predated the
> CONFIG_PPLUS work. If you can come up with a patch that adds mvme5100
> support to CONFIG_PPLUS, we can get rid of the MVME5100-specific stuff.
> (And, if you do, please look at Documentation/SubmittingPatches and the
> Developers Certificate of Origin).
This is true. When Randy Vinson did the CONFIG_PPLUS work, he decided
to initially just gather up all the boards that were covered (in a
suboptimal fashion) under PReP. The idea was to bring the other
standalone boards into CONFIG_PPLUS in the future, but nobody has
gotten around to it...until now, apparently.
-Matt
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Linux-2.6.9-rc2 kernel build for mvme5100
2004-09-22 16:33 ` Tom Rini
2004-09-22 16:47 ` Matt Porter
@ 2004-09-23 20:14 ` David Gardiner
1 sibling, 0 replies; 12+ messages in thread
From: David Gardiner @ 2004-09-23 20:14 UTC (permalink / raw)
To: Tom Rini; +Cc: linuxppc-dev
>I'll try and pick out the important changes and push them up. Thanks.
>
>
I think I'd rather fold the mvme5100 into pplus as later emails
discussed which would make the patch useless so please hold off.
Ta,
dg
^ permalink raw reply [flat|nested] 12+ messages in thread
end of thread, other threads:[~2004-09-23 20:13 UTC | newest]
Thread overview: 12+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-09-16 4:29 Linux-2.6.9-rc2 kernel build for mvme5100 David Gardiner
2004-09-16 5:36 ` Matt Porter
2004-09-16 7:54 ` David Gardiner
2004-09-20 17:32 ` Tom Rini
2004-09-20 19:23 ` Matt Porter
2004-09-20 22:55 ` David Gardiner
2004-09-21 0:12 ` David Gardiner
2004-09-22 16:33 ` Tom Rini
2004-09-22 16:47 ` Matt Porter
2004-09-23 20:14 ` David Gardiner
2004-09-21 9:15 ` Marius Groeger
2004-09-21 15:48 ` Tom Rini
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).