Quoting Corey Osgood <[EMAIL PROTECTED]>:
[EMAIL PROTECTED] wrote:
Quoting ron minnich <[EMAIL PROTECTED]>:
On 9/29/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]>
wrote:
device pci 2.0 off end # VGA compatible controller: Intel Corporation
82830 CGC
enabled it does not allocate the 0x00fec0
[EMAIL PROTECTED] wrote:
> Quoting ron minnich <[EMAIL PROTECTED]>:
>
>> On 9/29/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]>
>> wrote:
>>
>>> device pci 2.0 off end # VGA compatible controller: Intel Corporation
>>> 82830 CGC
>>>
>>> enabled it does not allocate the 0x00fec0 - 0x00fec000ff memory
Quoting ron minnich <[EMAIL PROTECTED]>:
> On 9/29/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
>> device pci 2.0 off end # VGA compatible controller: Intel Corporation
>> 82830 CGC
>>
>> enabled it does not allocate the 0x00fec0 - 0x00fec000ff memory
>> range. Is this because the VGA co
On 9/29/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> device pci 2.0 off end # VGA compatible controller: Intel Corporation
> 82830 CGC
>
> enabled it does not allocate the 0x00fec0 - 0x00fec000ff memory
> range. Is this because the VGA controller prefetches memory first?? Or
> is this ju
Quoting Marc Jones <[EMAIL PROTECTED]>:
>
>
> [EMAIL PROTECTED] wrote:
>> Quoting [EMAIL PROTECTED]:
>>
>>> Quoting [EMAIL PROTECTED]:
>>>
OK, I have a new booting problem. LB dies on the
i82801xx_enable_ioapic() function in 82801xx_lpc.c:
void i82801xx_enable_ioapic(struc
[EMAIL PROTECTED] wrote:
> Quoting [EMAIL PROTECTED]:
>
>> Quoting [EMAIL PROTECTED]:
>>
>>> OK, I have a new booting problem. LB dies on the
>>> i82801xx_enable_ioapic() function in 82801xx_lpc.c:
>>>
>>>
>>> void i82801xx_enable_ioapic(struct device *dev)
>>> {
>>> uint32_t reg32;
>>>
Quoting [EMAIL PROTECTED]:
> Quoting [EMAIL PROTECTED]:
>
>> OK, I have a new booting problem. LB dies on the
>> i82801xx_enable_ioapic() function in 82801xx_lpc.c:
>>
>>
>> void i82801xx_enable_ioapic(struct device *dev)
>> {
>> uint32_t reg32;
>> volatile uint32_t *ioapic_index = (vola
[EMAIL PROTECTED] wrote:
> OK, I have a new booting problem. LB dies on the
> i82801xx_enable_ioapic() function in 82801xx_lpc.c:
>
>
> void i82801xx_enable_ioapic(struct device *dev)
> {
> uint32_t reg32;
> volatile uint32_t *ioapic_index = (volatile uint32_t *)0xfec0;
> vo
Quoting [EMAIL PROTECTED]:
> OK, I have a new booting problem. LB dies on the
> i82801xx_enable_ioapic() function in 82801xx_lpc.c:
>
>
> void i82801xx_enable_ioapic(struct device *dev)
> {
> uint32_t reg32;
> volatile uint32_t *ioapic_index = (volatile uint32_t *)0xfec0;
> v
OK, I have a new booting problem. LB dies on the
i82801xx_enable_ioapic() function in 82801xx_lpc.c:
void i82801xx_enable_ioapic(struct device *dev)
{
uint32_t reg32;
volatile uint32_t *ioapic_index = (volatile uint32_t *)0xfec0;
volatile uint32_t *ioapic_data = (vol
Heh, oops, forgot a couple plus signs. Need to get some sleep, sorry!
-Corey
Corey Osgood wrote:
> Okay, on the MADT, I'm having a bit of trouble, LinuxBIOS is hanging
> while creating the checksum. I've attached my acpi_tables.c (and Rudolf,
> I'm sorry for not looking through yours more, I simp
Okay, on the MADT, I'm having a bit of trouble, LinuxBIOS is hanging
while creating the checksum. I've attached my acpi_tables.c (and Rudolf,
I'm sorry for not looking through yours more, I simply overlooked the
entire MADT portion of them and when they didn't build for me discarded
them). To be sp
* Corey Osgood <[EMAIL PROTECTED]> [070922 21:59]:
>> Linux never knows about your APICs...
>
> Odd, you need a Multiple APIC Descriptor Table for a single cpu? Looking at
> the spec, that seems to be the case, will get to work on it.
yes, because you have two apics ;)
>> have you tried booting
Stefan Reinauer wrote:
> * Corey Osgood <[EMAIL PROTECTED]> [070922 00:49]:
>
>> ACPI: Writing ACPI tables at f0400...
>> ACPI: * FACS
>> ACPI: * DSDT @ 000f04a2 Length 58a0
>> ACPI: * FADT
>> ACPI: added table 1/6 Length now 40
>>
>
> You don't have a MADT? Check acpi_tables.c
* Corey Osgood <[EMAIL PROTECTED]> [070922 00:49]:
> ACPI: Writing ACPI tables at f0400...
> ACPI: * FACS
> ACPI: * DSDT @ 000f04a2 Length 58a0
> ACPI: * FADT
> ACPI: added table 1/6 Length now 40
You don't have a MADT? Check acpi_tables.c from agami/aruma.c
Linux never knows about yo
* Corey Osgood <[EMAIL PROTECTED]> [070921 01:32]:
> .ACPI Error (evevent-0314): No installed handler for fixed event
> [] [20060707]
> ACPI Error (evevent-0314): No installed handler for fixed event
> [0002] [20060707]
> ACPI Error (evevent-0314): No installed handler for fixed event
>
* Corey Osgood <[EMAIL PROTECTED]> [070920 23:51]:
> What it pretty much boils down to is, what's required to set up
> APIC/IOAPIC in LinuxBIOS? I've tried using both my vt8237r stuff
> (originally posted here:
> http://www.linuxbios.org/pipermail/linuxbios/2007-August/023553.html,
> cn700 code has
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Yes.
R.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFG9FE83J9wPJqZRNURAgezAKCS55fayePNK6TmKo0huwuE/9P/PgCfbmJz
Y9yu05csIwvEh7F+i4ACwzQ=
=BZMj
-END PGP SIGNAT
Can you send your vt8237r.c as well?
Thanks,
Corey
--
linuxbios mailing list
linuxbios@linuxbios.org
http://www.linuxbios.org/mailman/listinfo/linuxbios
Okay, finally managed to get the kernel panic out to go to the serial
console, and I'm not sure what's going on. This happens with the ACPI
base either at 0x400 or 0x500, with either a fixed factory dsdt or
Rudolf's modified, or without any ACPI at all. This kernel boots with
the factory BIOS, and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Corey Osgood wrote:
> Just realized thats where my smbus IO base is. I'll try moving things
> around a bit, I don't even need smbus at the moment.
> Heh, I went ahead and dumped my mptable, even though this is a single
> processor system. The mptable
Rudolf Marek wrote:
> Thanks, I'll have a look at these tomorrow. For some reason, ACPI on my
>> system doesn't work (produces the error I had before) if the base is set
>> to 0x500, but it does work with 0x400 (the factory slot). Also, a quick
>>
>
> Maybe you have something at 0x500, use the i
Thanks, I'll have a look at these tomorrow. For some reason, ACPI on my
> system doesn't work (produces the error I had before) if the base is set
> to 0x500, but it does work with 0x400 (the factory slot). Also, a quick
>
Maybe you have something at 0x500, use the isadump -f 0x500 from
lm-sen
Rudolf Marek wrote:
> Hi again,
>
> I'm attaching my ACPI/IRQ related files, ACPI on my machine works (I'm
> getting
> power button events) and all IRQ are working too. I'm not supporting
> the PIC at all.
>
> You need to compile the dsdt.asl with iasl -tc and then rename it from
> dsdt.hex
> to ds
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Oh sorry one more table for a shiny morning ;)
Rudolf
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFG82qX3J9wPJqZRNURAhJJAKC22uObWW4Y2ExAaeEoujoVha+IjACgo8NC
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi again,
I'm attaching my ACPI/IRQ related files, ACPI on my machine works (I'm getting
power button events) and all IRQ are working too. I'm not supporting the PIC at
all.
You need to compile the dsdt.asl with iasl -tc and then rename it from dsdt
Rudolf Marek wrote:
>
> You have undefined NEED_LAPIC
>
> #if NEED_LAPIC == 1
> ...
> #else
>printk_info("Disabling local apic...");
> #endif...
>
> RTFS ;)
>
> Rudolf
Yep, I suppose adding the CONFIG_IOAPIC option MIGHT help things a
little bit (not sure how I missed it, checked the Optio
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
You have undefined NEED_LAPIC
#if NEED_LAPIC == 1
...
#else
printk_info("Disabling local apic...");
#endif...
RTFS ;)
Rudolf
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.
Forgot the boot log, here it is.
-Corey
Corey Osgood wrote:
> I'm lost here, with the factory BIOS IRQs are handled through IOAPIC,
> but it seems that LinuxBIOS keeps disabling it. I've got both ACPI
> tables and irq tables (modified to be somewhat correct), and ioapic
> should be enabled throug
I'm lost here, with the factory BIOS IRQs are handled through IOAPIC,
but it seems that LinuxBIOS keeps disabling it. I've got both ACPI
tables and irq tables (modified to be somewhat correct), and ioapic
should be enabled through the vt8237r. The ioapic base seems to be
right, and so do all the re
30 matches
Mail list logo
