Hi,
Which filesystem should I use for diskonchip? Should I use ths True FFS
or can I use the NFTL?
_________________________________________________________________
Love shopping online? Get this e credit card.
http://server1.msn.co.in/features/amex/ Save cost, add value!
Output
-----邮件原件-----
发件人: YhLu
发送时间: 2003年12月3日 18:34
收件人: YhLu; ebiederman(a)lnxi.com
抄送: ron minnich; Stefan Reinauer; linuxbios(a)clustermatic.org
主题: Tyan S2885
Eric,
I found in amdk8_scan_root_bus in northbridge/amd/amdk8/northbridge.c
You put
/* Unmap all of the other pci busses */
for(reg = 0xe0; reg <= 0xec; reg += 4) {
f1_write_config32(reg, 0);
}
Why you need to clear that? After you clear that, I can not see the 8151 and
AGP in s2885.
PS:
I have reversed the scan sequence to make sure HT scan 8111 at first and
then 8151.
Regards
Yinghai Lu
Hi,
* ron minnich <rminnich(a)lanl.gov> [031202 00:28]:
> > {0,0xa0, {{0x2, 0xdeb8}, {0x3, 0xdeb8}, {0x4, 0xdeb8}, {0x1, 0xdeb8}}, 0x1, 0},
>
> > pci_assign_irqs(2, 0x5, dualenetbIrq);''
> > in addition i had to play with the irq lists.
>
> eek. You know that this is exactly the wrong way to do this and why, I
> assume. But it works, so keep it for now. But this will never go into the
> CVS.
Do we agree that interrupts should be _unassigned_ during firmware
execution and set by the OS only? Another way of handling this might be
to set some default values and allow the OS to reconfigure those.
A PIRQ-Table has to contain
* one entry for each PCI device that needs an interrupt
* one entry for each peer bus to be visible.
It seems we know these parameters in-system already and can generate a
valid table assuming some fixed parameters (cycling interrupts a la
{{0x2, 0xdeb8}, {0x3, 0xdeb8}, {0x4, 0xdeb8}, {0x1, 0xdeb8}}
and a fixed mask of 0xdeb8.
> irq_table.c is for linux, it tells linux how the irqs are wired up. In an
> ideal world, linuxbios would hand the irq table to linux or plan9 or *bsd
> and those OSes would do everything correctly. In our world, each of these
> OSes get it wrong often enough that we have to now assign it directly. I
> had hoped to avoid IRQ assignment in linuxbios but it seems that we have
> no choice -- too many busted hardware/OS bits out there.
Not to forget the mptable - that contains additional information on
which busses are available - information that Linux obviously don't like
to read from there but from the irq table.
Stefan
--
Stefan Reinauer, SUSE LINUX AG
Teamleader Architecture Development
Stefan,
Which builds are broken? I thought I checked all configurations built
after the change (apart from the VIA which Ron was working on.) and
modified any that had problems.
My hope was that this change would make the use of options more
logical and consistent. The intention is that parts set default
values for any options that they require or are specific to the part.
Then when all the parts are put together in a target configuration
file, these default values can be overridden for the specific build.
I was also toying with the idea of allowing some options to be
read-only, which I think would address your concern.
Apologies for breaking things. I try to build all targets after any
change like this to make sure things are still working.
Greg
At 4:16 PM +0100 11/6/03, Stefan Reinauer wrote:
>Hi,
>
>most of the builds are broken again since "config" in the mainboard
>config file now has to be renamed to "default". On the one hand I see
>the reason for most of these changes, even though I am not sure if
>we want to suggest that some stuff can be overridden in the target
>config file, like:
>
>-option CONFIG_IOAPIC=1
>+default CONFIG_IOAPIC=1
>
>Can those changing elementary stuff like this that breaks all builds try
>to apply some regexps on the Config files so that other builds don't
>break? Getting further is somewhat hard currently since the code almost
>instantly breaks after the last fixes are checked in..
>
>Stefan
>
>--
> Stefan Reinauer, SUSE LINUX AG
>Teamleader Architecture Development
>_______________________________________________
>Linuxbios mailing list
>Linuxbios(a)clustermatic.org
>http://www.clustermatic.org/mailman/listinfo/linuxbios
Hi,
I could not find any ipl code for sc1200 (nano mainboard). Which should I
mention in the config file for docipl? Please give me suggestion.
Thanks in advance.
_________________________________________________________________
Contact brides & grooms FREE! Only on www.shaadi.com.
http://www.shaadi.com/ptnr.php?ptnr=hmltag Register now!
Hi to all, today i make EPIA-M 10000 rom image. i compile to have VGA and
Filo,
after apply patch of Dave Ashley and info from Takeshi about RAM ammount
VGA now is found by the system but ....
In attach you have the output log ....
Can someone tell me where i wrong?
Dave Ashley reply:
You haven't applied all the patch, specifically the handler
for the unsupported bios interrupts.
This is the bug where it just gets into an endless loop
of bios interrupts, so the program needs to exit the
bios somehow. -Dave
Hi , can some one tell me where to look ....
i made the patch ....where to look Dave to know if the patch is ok ?
Thanks.
Santi Mirenna
At 11.59 03/12/2003, you wrote:
>Hi Santi,
>
>At a minimum you need to check that your arch/i386/lib/idt.c file has the
>Int 21 and Unsupported Interrupt handler calling code installed:
>
>@@ -175,9 +175,18 @@
> eax = 64 * 1024;
> ret = 0;
> break;
>+#ifdef CONFIG_INT21HANDLER
>+ case 0x15:
>+ ret=handleint21( &edi, &esi, &ebp, &esp,
>+ &ebx, &edx, &ecx, &eax, &flags);
>+ break;
>+#endif
> default:
> printk_info(__FUNCTION__ ": Unsupport int #0x%x\n",
> intnumber);
>+#ifdef CONFIG_UNSUPPORTINT_RECOVER
>+ unsupportint_recover();
>+#endif
> break;
>
>
>and that arch/i386/lib/vgabios.c and mainboard/via/epia-m/mainboard.c
>respectively have the actual handler routines:
>
>@@ -145,6 +145,13 @@
> __asm__ (".text\n""real_mode_switch_end:\n");
> extern char real_mode_switch_end[];
>
>+#ifdef CONFIG_UNSUPPORTINT_RECOVER
>+void unsupportint_recover(void)
>+{
>+ __asm__ __volatile__ ( " jmp vgarestart \n" );
>+}
>+#endif
>+
>
>and
>
>@@ -92,3 +176,33 @@
> final_southbridge_fixup();
> }
>
>+int handleint21( unsigned long *edi, unsigned long *esi, unsigned long *ebp,
>+ unsigned long *esp, unsigned long *ebx, unsigned
>long *edx,
>+ unsigned long *ecx, unsigned long *eax, unsigned
>long *flags)
>+{
>+int res=-1;
>+ switch(*eax&0xffff)
>+ {
>+ case 0x5f19:
>+ break;
>+ case 0x5f18:
>+ *eax=0x5f;
>+ *ebx=0x15; // MCLK = 133, 32M frame buffer
>+ res=0;
>+ break;
>+ case 0x5f02:
>+ *eax=0x5f;
>+ *ebx=0 | (3<<8);
>+ *ecx=5 | (0<<8) | (0<<16);
>+ res=0;
>+ break;
>+ case 0x5f0f:
>+ *eax=0x5f;
>+ *ebx=0;
>+ *ecx=0;
>+ *edx=0;
>+ res=0;
>+ break;
>+ }
>+ return res;
>+}
>
>
>NOTE: It's possible that you may have patch these in by hand as the
>original diffs were from an older version of the codebase and things may
>have changed since then.
All the patch is ok and I get the CVS of 05 2003-July
>A quick check is to make sure there are no *.rej files present which might
>indicate a patch operation has failed.
all files are patched
>The diffs aren't large, so it's probably worthing checking them by hand to
>make sure the patches have been properly applied.
>
>Cheers
>
>Ian
>
>At 09:31 03/12/2003, Santi Mirenna wrote:
>>Hi to all, today i make EPIA-M 10000 rom image. i compile to have VGA and
>>Filo,
>>after apply patch of Dave Ashley and info from Takeshi about RAM ammount
>>VGA now is found by the system but ....
>>In attach you have the output log ....
>>Can someone tell me where i wrong?
>>
>>Dave Ashley reply:
>>
>>You haven't applied all the patch, specifically the handler
>>for the unsupported bios interrupts.
>>This is the bug where it just gets into an endless loop
>>of bios interrupts, so the program needs to exit the
>>bios somehow. -Dave
>>
>>Hi , can some one tell me where to look ....
>>i made the patch ....where to look Dave to know if the patch is ok ?
>>
>>Thanks.
>>
>>Santi Mirenna
Eric,
The Kernel is used 2.4.22 and I compiled it in ADM64 mode.
The LAN device is Broadcom 5704 and driver should be tg3.
The SCSI device (LSI SCSI 53c1030 -- onboard and Adaptec 29320 addon card)
all can not be initialized in Linux Kernal.
Regards
YH.
>> 3. southbridge/amd/amd8131/amd8131_bridge.c: update ioapic_anable to
enable
>> PCI-X MASTER Mode.
>Why is this necessary? Previously it has been the policy to not set
>the master enables any more than is necessary for proper operation
>of the devices. Unless I am mistaken not setting the master enables is
>very much in spec for pci devices.
Eric,
Otherwise I can not use LAN and SCSI devices in PCI-X in Linux.
For Broadcom NIC, I can not ifconfig and ping.
For SCSI, I just can not get through the SCSI initialize in Linux kernel.
YH.
