xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Sergey Tovpeko <tsv.devel@gmail.com>
To: Sander Eikelenboom <linux@eikelenboom.it>
Cc: weidong.han@intel.com, xen-devel@lists.xensource.com,
	"Mr. Teo En Ming (Zhang Enming)" <space.time.universe@gmail.com>,
	xen-users@lists.xensource.com
Subject: Re: Xen VGA graphics passthru wiki page
Date: Wed, 17 Mar 2010 18:59:59 +0300	[thread overview]
Message-ID: <4BA0FC7F.3080609@gmail.com> (raw)
In-Reply-To: <1388502422.20100317150505@eikelenboom.it>

In fact, we got an engineer sample sometime ago with RD890 chipset

lspci output:

00:00.0 Host bridge: ATI Technologies Inc RD890 Northbridge only dual 
slot (2x16) PCI-e GFX Hydra part (rev 02)

And i tested VGA passthrough on RD890, not on SR5690/SR5670.  And it has 
IOMMU inside.

> Hello Pasi,
>
> It should have an iommu, but the mobo's are just on the market, haven't tested it myself.
>
> --
> Sander
>
> Wednesday, March 17, 2010, 3:02:31 PM, you wrote:
>
>   
>> On Wed, Mar 17, 2010 at 11:47:22AM +0100, Sander Eikelenboom wrote:
>>     
>>> Hello Sergey,
>>>
>>> Ah if i look at the spec sheets it's not a RD-890 chipset, but a opteron server chipset.
>>>
>>>       
>
>   
>> So is RD-890 still ok, aka it has IOMMU support? Has anyone tested it with Xen? 
>> Should I remove RD-890 from the wiki pages?
>>     
>
>   
>>> http://www.tyan.com/datasheets/d_S8212.pdf
>>>
>>> Chipset:
>>> AMD SR5690 + SP5100 (S8212WGM3NR/S8212GM3NR)
>>> AMD SR5670 + SP5100 (S8212GM3NRLE/S8212GM3NR-LE))
>>>
>>> Nevertheless good to hear vga passthrough works for you.
>>>
>>>       
>
>   
>> Ok so I should add this one.. which one of the various models above is your mb? 
>>     
>
>   
>> -- Pasi
>>     
>
>   
>>> --
>>>
>>> Sander
>>>
>>>
>>>
>>> Wednesday, March 17, 2010, 11:33:21 AM, you wrote:
>>>
>>>       
>>>> Hello, Sander,
>>>>         
>>>>> Sergey, what specific brand/type mobo do you use ?
>>>>>
>>>>>   
>>>>>           
>>>> The motherboard is TYAN s8212.
>>>>         
>>>
>>>
>>> -- 
>>> Best regards,
>>>  Sander                            mailto:linux@eikelenboom.it
>>>
>>>       
>
>
>
>   

  reply	other threads:[~2010-03-17 15:59 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-13  0:22 Xen VGA graphics passthru wiki page Pasi Kärkkäinen
2010-03-15  2:25 ` Han, Weidong
2010-03-15 10:24 ` [Xen-devel] " Sergey Tovpeko
2010-03-16 16:45   ` Pasi Kärkkäinen
2010-03-16 17:38     ` Sander Eikelenboom
2010-03-17 10:33       ` [Xen-devel] " Sergey Tovpeko
2010-03-17 10:47         ` Sander Eikelenboom
2010-03-17 14:02           ` Pasi Kärkkäinen
2010-03-17 14:05             ` [Xen-devel] " Sander Eikelenboom
2010-03-17 15:59               ` Sergey Tovpeko [this message]
2010-03-18 16:18                 ` Pasi Kärkkäinen
2010-03-19 10:15                   ` [Xen-devel] " Sergey Tovpeko
2010-03-19 10:27                     ` Sander Eikelenboom
2010-03-19 17:40                       ` Pasi Kärkkäinen

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=4BA0FC7F.3080609@gmail.com \
    --to=tsv.devel@gmail.com \
    --cc=linux@eikelenboom.it \
    --cc=space.time.universe@gmail.com \
    --cc=weidong.han@intel.com \
    --cc=xen-devel@lists.xensource.com \
    --cc=xen-users@lists.xensource.com \
    /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;
as well as URLs for NNTP newsgroup(s).