<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
On 9/23/10 11:09 PM, Uwe Hermann wrote:<br>
<blockquote cite="mid:20100923210920.GI3256@greenwood" type="cite">
<div class="moz-text-plain" wrap="true" graphical-quote="true"
style="font-family: -moz-fixed; font-size: 12px;"
lang="x-western">
<pre wrap="">For now I marked all chipsets where we have Debug Port code as untested,
I have a feeling the functionality was rarely tested recently (or at
all) so we should only mark those chipsets as tested where we actually
have recent test reports.
</pre>
</div>
</blockquote>
Last time I tested on i945 I was able to get output if I called the
debug port output function directly, but it seemed that you would
not get any output from printk as it simply was not hooked up. Has
that changed since then?<br>
<br>
<blockquote cite="mid:20100923210920.GI3256@greenwood" type="cite">
<div class="moz-text-plain" wrap="true" graphical-quote="true"
style="font-family: -moz-fixed; font-size: 12px;"
lang="x-western">
<pre wrap="">Hook up all AMD SB600/SB700 boards to the EHCI Debug Port infrastructure.
Without a (currently) dummy set_debug_port() function the build fails,
this may or may not be fixed differently in the future.
Manually build-tested on all SB600/SB700 boards, and tested on hardware on
one SB600 board I own, works fine.
Signed-off-by: Uwe Hermann <a moz-do-not-send="true" class="moz-txt-link-rfc2396E" href="mailto:uwe@hermann-uwe.de"><uwe@hermann-uwe.de></a>
</pre>
</div>
</blockquote>
Acked-by: Stefan Reinauer <a class="moz-txt-link-rfc2396E" href="mailto:stepan@coresystems.de"><stepan@coresystems.de></a><br>
<br>
</body>
</html>