[COMMIT] EPIA irq fixed, thanks to Kevin Hester

[Andrew Ip]

Finally...  We have got the irq assignment working.
Here are the checkins

cpu/c3/premtrr.inc
lib/newpci.c
- added added pci_level_irq and pci_assign_irqs
lib/vsprintf.c
southbridge/via/vt8231/ideconfig.inc
mainboard/via/epia/Config
mainboard/via/epia/irq_tables.c
mainboard/via/epia/mainboard.c
northbridge/via/vt694/northbridge.c
southbridge/via/vt8231/southbridge.c
superio/via/vt8231/setup_ethernet.inc

However there are still some minor problems, eg
1. linuxbios willl hang at pci scanning devfn > 0xa8 when rebooting
2. linux might hange when pci scanning devfn > 0xa8
That could be a hardware problem according to Ron.
3. pirq semi-working.  Although irq is being assigned correctly, device doesn't
   work.  Luckily we can force irq.

Kevin still has some extra stuffs to add, eg, non-block console display.  I
will work on it later.

Thanks Kevin and Ron for all the help.

Happy hacking.

-Andrew

[Ronald G. Minnich]

On Sat, 14 Dec 2002, Andrew Ip wrote:
> linuxbios willl hang at pci scanning devfn > 0xa8 when rebooting
> linux might hange when pci scanning devfn > 0xa8
>
> That could be a hardware problem according to Ron.

I've seen this problem, but ONLY on VIA north bridges derived from the 
8601. Hence I still blame the chipset.

So we can build a working EPIA at this point?

ron

[Andrew Ip]

> I've seen this problem, but ONLY on VIA north bridges derived from the 
> 8601. Hence I still blame the chipset. 
> So we can build a working EPIA at this point?

Basically yes.  If you have the above problem, you probably need to change the
kernel to skip the pci probe.

-Andrew

[Steve M. Gehlbach]

> > I've seen this problem, but ONLY on VIA north bridges derived from the
> > 8601. Hence I still blame the chipset.
> > So we can build a working EPIA at this point?
>
> Basically yes.  If you have the above problem, you probably need
> to change the
> kernel to skip the pci probe.
>
> -Andrew

The EPIA mini-ITX that I have boots fine with 2.4.18 with the BIOS that came
with it.  Doesn't this mean that it is a bridge setup issue? Or does it not
happen on all boards?

-Steve

[Andrew Ip]

> The EPIA mini-ITX that I have boots fine with 2.4.18 with the BIOS that came
> with it.  Doesn't this mean that it is a bridge setup issue? Or does it not
> happen on all boards?

Normal bios boots ok but not with LinuxBIOS.  There could be some magic setting
for that.

-Andrew

[Ronald G. Minnich]

BTW I built a linuxbios for epia today and got ... nothing :-(

no POST, no serial out, nothing.

I'll try more tomorrow.

ron

[Ronald G. Minnich]

On Mon, 16 Dec 2002, Steve M. Gehlbach wrote:
> The EPIA mini-ITX that I have boots fine with 2.4.18 with the BIOS that came
> with it.  Doesn't this mean that it is a bridge setup issue? Or does it not
> happen on all boards?

is the 2.4.18 using DIRECT, ANY, or PCIBIOS for PCI configuration? try 
wiring to direct.

ron

[Steve M. Gehlbach]

> is the 2.4.18 using DIRECT, ANY, or PCIBIOS for PCI configuration? try
> wiring to direct.
>
> ron

Not sure, I am not familiar with this setting; it is offline at the moment.
Is this the pci=xxxx command line parameter? But it was just default debian
woody, whatever it defaulted to.  It's at the office, I can boot it tomorrow
and see.  What do I look for?

-Steve

[Ronald G. Minnich]

On Mon, 16 Dec 2002, Steve M. Gehlbach wrote:
> Not sure, I am not familiar with this setting; it is offline at the moment.

it will be in the .config for your kernel. For my smartcore, with DIRECT, 
looks like this:
# CONFIG_PCI_GOBIOS is not set
CONFIG_PCI_GODIRECT=y
# CONFIG_PCI_GOANY is not set
CONFIG_PCI_DIRECT=y

[Steve M. Gehlbach]

Below is what I normally use, so I am pretty sure this is it:

# General setup
#
CONFIG_NET=y
CONFIG_PCI=y
# CONFIG_PCI_GOBIOS is not set
# CONFIG_PCI_GODIRECT is not set
CONFIG_PCI_GOANY=y
CONFIG_PCI_BIOS=y
CONFIG_PCI_DIRECT=y
CONFIG_PCI_NAMES=y
# CONFIG_EISA is not set
# CONFIG_MCA is not set
# CONFIG_HOTPLUG is not set
# CONFIG_PCMCIA is not set
# CONFIG_HOTPLUG_PCI is not set
CONFIG_SYSVIPC=y
# CONFIG_BSD_PROCESS_ACCT is not set
CONFIG_SYSCTL=y
CONFIG_KCORE_ELF=y
# CONFIG_KCORE_AOUT is not set
# CONFIG_BINFMT_AOUT is not set
CONFIG_BINFMT_ELF=y
# CONFIG_BINFMT_MISC is not set
# CONFIG_PM is not set
# CONFIG_APM is not set

-Steve
> -----Original Message-----
> From: Ronald G. Minnich [mailto:[e-mail]]
> Sent: Monday, December 16, 2002 9:08 PM
> To: Steve M. Gehlbach
> Cc: [e-mail]
> Subject: RE: [COMMIT] EPIA irq fixed, thanks to Kevin Hester
>
> On Mon, 16 Dec 2002, Steve M. Gehlbach wrote:
> > Not sure, I am not familiar with this setting; it is offline at
>
> the moment.
>
> it will be in the .config for your kernel. For my smartcore, with DIRECT,
> looks like this:
> # CONFIG_PCI_GOBIOS is not set
> CONFIG_PCI_GODIRECT=y
> # CONFIG_PCI_GOANY is not set
> CONFIG_PCI_DIRECT=y

[Ronald G. Minnich]

On Mon, 16 Dec 2002, Steve M. Gehlbach wrote:
> # CONFIG_PCI_GOBIOS is not set
> # CONFIG_PCI_GODIRECT is not set
> CONFIG_PCI_GOANY=y
> CONFIG_PCI_BIOS=y
> CONFIG_PCI_DIRECT=y
> CONFIG_PCI_NAMES=y

so you won't see the bug, as you use the pcibios.

ron

[Steve M. Gehlbach]

> > # CONFIG_PCI_GOBIOS is not set
> > # CONFIG_PCI_GODIRECT is not set
> > CONFIG_PCI_GOANY=y
> > CONFIG_PCI_BIOS=y
> > CONFIG_PCI_DIRECT=y
> > CONFIG_PCI_NAMES=y
>
> so you won't see the bug, as you use the pcibios.
>
> ron

Thanks, I get the point now.

-Steve

[Steve M. Gehlbach]

> BTW I built a linuxbios for epia today and got ... nothing :-(
>
> no POST, no serial out, nothing.
>
> I'll try more tomorrow.
>
> ron

Worked for me.

-Steve