public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Stefan Schweizer <sschweizer-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: "Stefan Dösinger" <stefandoesinger-RbZlAiThDcE@public.gmane.org>
Cc: Matthias Hentges
	<mailinglisten-H4PcyxPeSRnR7s880joybQ@public.gmane.org>,
	Oliver Dawid <oliver-csNNzRR391izQB+pC5nmwQ@public.gmane.org>,
	acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: S3 broken Samsung P35 - howto debug?
Date: Thu, 25 Nov 2004 14:57:48 +0100	[thread overview]
Message-ID: <e7963922041125055775846413@mail.gmail.com> (raw)
In-Reply-To: <200411251403.02800.stefandoesinger-RbZlAiThDcE@public.gmane.org>

On Thu, 25 Nov 2004 14:03:02 +0100, Stefan Dösinger
<stefandoesinger-RbZlAiThDcE@public.gmane.org> wrote:
> The danger is that it really becomes a killer. As I said, I just copied
> assembler code to C code without really knowing what it does. So I do not
> recommend it until someone from ATI has a look at it. So far I haven't mailed
> ATI, and I do not think I'll get help from them. Ole predicted the answer
> "Use the bios"

I would recommend you to ask ATI and just try it. I think they are
also happy if you solve problems with their drivers, so you should be
welcome there.


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/

  parent reply	other threads:[~2004-11-25 13:57 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-21 15:00 S3 broken Samsung P35 - howto debug? Oliver Dawid
     [not found] ` <200411211600.01820.od-VRmHG7Xu4f31qYPpFx2fzhvVK+yQ3ZXh@public.gmane.org>
2004-11-21 18:05   ` Pavel Machek
2004-11-21 19:08   ` Matthias Hentges
2004-11-22  8:20     ` Oliver Dawid
     [not found]       ` <41A1A145.4090006-csNNzRR391izQB+pC5nmwQ@public.gmane.org>
2004-11-22 12:26         ` Matthias Hentges
2004-11-24 10:23     ` Oliver Dawid
     [not found]       ` <41A4613F.2020905-csNNzRR391izQB+pC5nmwQ@public.gmane.org>
2004-11-24 12:54         ` Stefan Dösinger
     [not found]           ` <200411241354.53598.stefandoesinger-RbZlAiThDcE@public.gmane.org>
2004-11-24 16:28             ` Matthias Hentges
2004-11-24 17:42               ` Christoph Tavan
2004-11-25  7:02             ` Oliver Dawid
2004-11-24 13:13         ` Matthias Hentges
     [not found] ` <200411242012.36750.stefandoesinger@gmx.at>
     [not found]   ` <1101328293.7299.15.camel@mhcln03>
2004-11-24 21:21     ` Stefan Dösinger
     [not found]       ` <200411242221.45175.stefandoesinger-RbZlAiThDcE@public.gmane.org>
2004-11-25  6:41         ` Matthias Hentges
2004-11-25 13:03           ` Stefan Dösinger
     [not found]             ` <200411251403.02800.stefandoesinger-RbZlAiThDcE@public.gmane.org>
2004-11-25 13:57               ` Stefan Schweizer [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-11-24 15:01 Pallipadi, Venkatesh

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=e7963922041125055775846413@mail.gmail.com \
    --to=sschweizer-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=mailinglisten-H4PcyxPeSRnR7s880joybQ@public.gmane.org \
    --cc=oliver-csNNzRR391izQB+pC5nmwQ@public.gmane.org \
    --cc=stefandoesinger-RbZlAiThDcE@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