From: Daniel Drake <dan-LrsmPHowOvpd3aXB8m+yKQ@public.gmane.org>
To: "Luis Miguel García" <ktech-39ZsbGIQGT7e5aOfsHch1g@public.gmane.org>
Cc: David Ford
<david+challenge-response-qokYbnrgTHEgsBAKwltoeQ@public.gmane.org>,
akpm-LL/9OlyS9hIAvxtiuMwx3w@public.gmane.org,
acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
a.verweij-oe7qfRrRQfeEZXFvZSAUrfP6llvjuJOh@public.gmane.org
Subject: Re: acpi problem with nforce motherboards and ethernet
Date: Fri, 06 Feb 2004 09:47:02 +0000 [thread overview]
Message-ID: <40236296.6040503@reactivated.net> (raw)
In-Reply-To: <4022B55B.1090309-39ZsbGIQGT7e5aOfsHch1g@public.gmane.org>
Luis Miguel García wrote:
> By the way, is anyone involved in solving the IO-APIC thing in nforce
> motherboards? Anyone trying a different approach? Anyone contacting
> nvidia about this problem?
Ross said in previous mails that he had tried to contact nvidia through
various methods, and had not recieved a response.
He also mentioned that AMD were being much more responsive, and he had a
support request open with them, which he was assured was being investigated.
But yeah, doesn't look like we are getting anywhere with the manufacturers...
Daniel
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
next prev parent reply other threads:[~2004-02-06 9:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-05 19:25 acpi problem with nforce motherboards and ethernet Luis Miguel García
[not found] ` <402298C7.5050405-39ZsbGIQGT7e5aOfsHch1g@public.gmane.org>
2004-02-05 19:44 ` David Ford
[not found] ` <40229D2C.20701-qokYbnrgTHEgsBAKwltoeQ@public.gmane.org>
2004-02-05 21:27 ` Luis Miguel García
[not found] ` <4022B55B.1090309-39ZsbGIQGT7e5aOfsHch1g@public.gmane.org>
2004-02-05 23:40 ` Andrew Morton
[not found] ` <20040205154059.6649dd74.akpm-3NddpPZAyC0@public.gmane.org>
2004-02-06 0:08 ` Prakash K. Cheemplavam
2004-02-06 0:14 ` Craig Bradney
[not found] ` <1076026496.16107.23.camel-V9bJ71E8C7qMuHbpHUh99CT4j+jCus6s@public.gmane.org>
2004-02-06 0:22 ` Luis Miguel García
[not found] ` <4022DE3C.1080905-39ZsbGIQGT7e5aOfsHch1g@public.gmane.org>
2004-02-06 0:38 ` Prakash K. Cheemplavam
2004-02-06 0:46 ` [ACPI] " Luis Miguel García
[not found] ` <4022E3C8.4020704-39ZsbGIQGT7e5aOfsHch1g@public.gmane.org>
2004-02-06 0:59 ` Craig Bradney
2004-02-06 0:56 ` Craig Bradney
2004-02-06 23:33 ` Maciej W. Rozycki
2004-02-07 2:50 ` [ACPI] " Andi Kleen
[not found] ` <Pine.LNX.4.55.0402070021210.12260-rsPqkUlH4Vdx0R2ya2r/wqsMm+1xrEX8@public.gmane.org>
2004-02-07 6:29 ` Luis Miguel García
2004-02-06 9:47 ` Daniel Drake [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-02-05 17:41 Luis Miguel García
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=40236296.6040503@reactivated.net \
--to=dan-lrsmphowovpd3axb8m+ykq@public.gmane.org \
--cc=a.verweij-oe7qfRrRQfeEZXFvZSAUrfP6llvjuJOh@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=akpm-LL/9OlyS9hIAvxtiuMwx3w@public.gmane.org \
--cc=david+challenge-response-qokYbnrgTHEgsBAKwltoeQ@public.gmane.org \
--cc=ktech-39ZsbGIQGT7e5aOfsHch1g@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox