From: Stefan Smietanowski <stesmi@stesmi.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: Matthew Garrett <mgarrett@chiark.greenend.org.uk>,
Dave Airlie <airlied@linux.ie>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] reset VGA adapters via BIOS on resume... (non-fbdev/con)
Date: Sat, 23 Jul 2005 08:53:00 +0200 [thread overview]
Message-ID: <42E1E94C.3000703@stesmi.com> (raw)
In-Reply-To: <20050723004745.GA7868@atrey.karlin.mff.cuni.cz>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Pavel Machek wrote:
> Hi!
>
>
>>>Unfortunately, if you only get printk() working after you ran
>>>userspace app... well it makes debugging things like SATA
>>>"interesting". So I quite like this patch.
>>
>>Most interesting laptop vendors have at least one model in each range
>>with a serial port, which makes this sort of thing a bit easier.
>
>
> Well, we have debugged with beeps, but... It would be cool if someone
> got usb debug mode working but... and there are hardware debuggers.
>
> Anyway, this patch is really good, and enables S3 to work on more
> machines. Thats good. It is not intrusive and I'll probably (try to)
> push it.
If kdb is your thing then SGI has gotten kdb work over USB using
OHCI chipsets. They haven't done UHCI (Yet?).
// Stefan
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (MingW32)
iD8DBQFC4elMBrn2kJu9P78RAlqqAJ4iKFeCf4Iomic7UzyWNLLztIqXkgCggc4L
xyzG4KWvlUT15roBjWhtMhE=
=j79y
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2005-07-23 6:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-22 18:52 [PATCH] reset VGA adapters via BIOS on resume... (non-fbdev/con) Dave Airlie
2005-07-22 23:17 ` Matthew Garrett
2005-07-23 0:31 ` Pavel Machek
2005-07-23 0:36 ` Matthew Garrett
2005-07-23 0:47 ` Pavel Machek
2005-07-23 6:53 ` Stefan Smietanowski [this message]
2005-07-24 6:08 ` Keith Owens
2005-07-25 6:39 ` Stefan Seyfried
2005-07-25 7:43 ` Dave Airlie
2005-07-25 7:48 ` Stefan Seyfried
2005-07-23 19:55 ` Alan Cox
2005-07-23 22:37 ` Dave Airlie
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=42E1E94C.3000703@stesmi.com \
--to=stesmi@stesmi.com \
--cc=airlied@linux.ie \
--cc=linux-kernel@vger.kernel.org \
--cc=mgarrett@chiark.greenend.org.uk \
--cc=pavel@ucw.cz \
/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