X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C80A2B.84449481@onstor-exch02.onstor.net>; Mon, 8 Oct 2007 20:18:59 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-class: urn:content-classes:message
Subject: RE: cougar cf: right back where we started from
Date: Mon, 8 Oct 2007 20:18:59 -0800
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E05EF082C@onstor-exch02.onstor.net>
In-Reply-To: <20071008152202.41a5f3c5@ripper.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: cougar cf: right back where we started from
Thread-Index: AcgJ+ac/R2ron1abR8i07qQgk4rm8gAMY11A
References: <20071008152202.41a5f3c5@ripper.onstor.net>
From: "Brian Stark" <brian.stark@onstor.com>
To: "Andy Sharp" <andy.sharp@onstor.com>

Hey, this is good progress.  If I'm looking at the output correctly, it
looks like interrupts are going.  Not sure I know what irq56 and irq57
are, though...
=20

=20

> -----Original Message-----
> From: Andy Sharp=20
> Sent: Monday, October 08, 2007 3:22 PM
> To: Brian Stark
> Subject: cougar cf: right back where we started from
>=20
> Well, I'm not sure whether to cry or clap, but I've got=20
> cougar CF working as well as I ever got it working on the=20
> Boobcat.  That is, I can do everything except use it as a=20
> root device.  Sigh.  Double-sigh.
> Some kind of problem with paging from the CF which I haven't=20
> figured out yet but which shouldn't be happening.
>=20
> PCI: Fixups for bus 0000:00
> PCI: Scanning behind PCI bridge 0000:00:07.0, config 000000, pass 0
> PCI: Scanning behind PCI bridge 0000:00:07.1, config 000000, pass 0
> PCI: Scanning behind PCI bridge 0000:00:07.0, config 000000, pass 1
> PCI: Scanning behind PCI bridge 0000:00:07.1, config 000000, pass 1
> PCI: Bus scan for 0000:00 returning with max=3D08
> DEV: registering device: ID =3D '0000:00:00.0'
> DEV: registering device: ID =3D '0000:00:07.0'
> DEV: registering device: ID =3D '0000:00:07.1'
> DEV: registering device: ID =3D '0000:00:08.0'
>   got res [42000000:42000fff] bus [42000000:42000fff] flags=20
> 200 for BAR 0 of 0000:00:07.0
> PCI: moved device 0000:00:07.0 resource 0 (200) to 42000000
>   got res [42001000:42001fff] bus [42001000:42001fff] flags=20
> 200 for BAR 0 of 0000:00:07.1
> PCI: moved device 0000:00:07.1 resource 0 (200) to 42001000
> PCI: Bus 1, cardbus bridge: 0000:00:07.0
>   IO window: 00008000-000080ff
>   IO window: 00008400-000084ff
>   PREFETCH window: 44000000-47ffffff
>   MEM window: 48000000-4bffffff
> PCI: Bus 5, cardbus bridge: 0000:00:07.1
>   IO window: 00008800-000088ff
>   IO window: 00008c00-00008cff
>   PREFETCH window: 4c000000-4fffffff
>   MEM window: 50000000-53ffffff
> PCI: Enabling bus mastering for device 0000:00:07.0
> PCI: Enabling bus mastering for device 0000:00:07.1
> PCI: fixup irq: (0000:00:00.0) got 0
> PCI: fixup irq: (0000:00:07.0) got 56
> PCI: fixup irq: (0000:00:07.1) got 57
> PCI: fixup irq: (0000:00:08.0) got 0
> .
> .
> .
> Yenta: CardBus bridge found at 0000:00:07.0 [0000:0000]
> Yenta: Enabling burst memory read transactions
> Yenta: Using INTVAL to route CSC interrupts to PCI
> Yenta: Routing CardBus interrupts to PCI Yenta TI: socket=20
> 0000:00:07.0, mfunc 0x00000022, devctl 0x60
> Yenta: ISA IRQ mask 0x0000, PCI irq 56
> Socket status: 30000006
> pcmcia: parent PCI bridge I/O window: 0x0 - 0x1ffffff
> adjust_io: probe_io =3D 1
> cs: IO port probe 0x0-0x1ffffff: clean.
> pcmcia: parent PCI bridge Memory window: 0x41000000 - 0x5fffffff
> DEV: registering device: ID =3D 'pcmcia_socket0'
> Yenta: CardBus bridge found at 0000:00:07.1 [0000:0000]
> Yenta: Using INTVAL to route CSC interrupts to PCI
> Yenta: Routing CardBus interrupts to PCI Yenta TI: socket=20
> 0000:00:07.1, mfunc 0x00000022, devctl 0x60
> Yenta: ISA IRQ mask 0x0000, PCI irq 57
> Socket status: 30000010
> pcmcia: parent PCI bridge I/O window: 0x0 - 0x1ffffff
> adjust_io: probe_io =3D 1
> cs: IO port probe 0x0-0x1ffffff: clean.
> pcmcia: parent PCI bridge Memory window: 0x41000000 - 0x5fffffff
> DEV: registering device: ID =3D 'pcmcia_socket1'
> i2c /dev entries driver
> i2c-swarm.o: i2c SMBus adapter module for SiByte board
> DEV: registering device: ID =3D 'i2c-0'
> DEV: registering device: ID =3D 'i2c-0'
> DEV: registering device: ID =3D 'i2c-1'
> DEV: registering device: ID =3D 'i2c-1'
> DEV: registering device: ID =3D '0-0050'
> DEV: registering device: ID =3D '0-0054'
> DEV: registering device: ID =3D '0-004d'
> DEV: registering device: ID =3D '0-004e'
> DEV: registering device: ID =3D 'mgmtbus'
> .
> .
> .
> pccard: PCMCIA card inserted into slot 1
> cs: memory probe 0x41000000-0x5fffffff: excluding=20
> 0x42000000-0x427fffff 0x44000000-0x53ffffff
>=20
> pcmcia: registering new device pcmcia1.0
> DEV: registering device: ID =3D '1.0'
> .
> .
> .
> hda: CF 512MB, CFA DISK drive
> DEV: registering device: ID =3D 'ide0'
> ide0 at 0x000-0x007,0x00e on irq 57
> DEV: registering device: ID =3D '0.0'
> hda: max request size: 128KiB
> hda: 1028160 sectors (526 MB) w/0KiB Cache, CHS=3D1020/16/63
>  hda: hda1 hda2
> ide-cs: hda: Vpp =3D 0.0
> .
> .
> .
> and so forth
>=20
>=20
> I partitioned the CF card you have in there and copied a root=20
> filesystem onto it.  But as before it messes up badly when=20
> trying to page off of the device.
>=20
> I think it's time for a nap now....
>=20
> a
>=20
