Google Mail Calendar Documents Reader Web more »
Recently Visited Groups | Help | Sign in
Google Groups Home
comp.os.linux.development
About this group
Subscribe to this group
This is a Usenet group - learn more
Silicon Motion 712 (Lynx EM+) and AMD Alchemy
Options
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
   3 messages - Collapse all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Follow-up To:
Add Cc | Add Follow-up to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers that you hear
 
Ted Schroeder  
View profile   Translate to Translated (View Original)
 More options 22 Mar 2004, 18:40
Newsgroups: comp.os.linux.development.system, comp.os.linux.development, comp.os.linux.hardware
From: Ted Schroeder <t...@schroeder.net>
Date: Mon, 22 Mar 2004 10:40:25 -0800
Local: Mon 22 Mar 2004 18:40
Subject: Silicon Motion 712 (Lynx EM+) and AMD Alchemy
Reply to author | Forward | Print | Individual message | Show original | Report this message | Find messages by this author
We are building a system that has an AMD Alchemy chip and a Silicon Motion 712
(Lynx EM+) graphics subsystem. I want to run Linux on this system and am trying
to figure out how to deal with the (new) graphics chip. We currently have a
similar system based on the Epson chip, which has a framebuffer driver built
into the 2.4.20 kernel that we are using. I then build a kdrive (TinyX) X server
and use the framebuffer mechanism for talking to the screen. This all works
fine, except the Epson doesn't have enough memory bandwidth to drive both and
LCD and a CRT display at the same time which is a requirement of this particular
device.

So, now I need to make the SM712 chip work in a similar, low memory, low storage
environment.

Anyway, a couple of questions:

1) Can I just use the VESA frame buffer driver with this setup? (That is, VESA
claims to be x86 only, but will it work in this setup?)

2) If not, does a frame buffer driver exist for the SM712 chip?

Any help greatly appreciated.

Ted Schroeder
FreeHand Systems, Inc.


    Reply to author    Forward  
You must Sign in before you can post messages.
To post a message, you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Lewin A.R.W. Edwards  
View profile   Translate to Translated (View Original)
 More options 3 Apr 2004, 20:10
Newsgroups: comp.os.linux.development.system, comp.os.linux.development, comp.os.linux.hardware
From: la...@larwe.com (Lewin A.R.W. Edwards)
Date: 3 Apr 2004 11:10:05 -0800
Local: Sat 3 Apr 2004 20:10
Subject: Re: Silicon Motion 712 (Lynx EM+) and AMD Alchemy
Reply to author | Forward | Print | Individual message | Show original | Report this message | Find messages by this author

> fine, except the Epson doesn't have enough memory bandwidth to drive both and
> LCD and a CRT display at the same time which is a requirement of this
> 1) Can I just use the VESA frame buffer driver with this setup? (That is, VESA
> claims to be x86 only, but will it work in this setup?)

The question is kind of bass-ackwards. The VESA framebuffer driver is
not really "x86-specific" as such, but the whole idea is predicated on
the existence of a VESA BIOS in your target system. An extended int
10h call is made to set the video mode. If your system doesn't have a
VESA BIOS extension (which it won't if it's not a vanilla x86 system)
then the concept of using the VESA driver is meaningless.

> 2) If not, does a frame buffer driver exist for the SM712 chip?

There is no direct kernel support for the Lynx series. Are you
planning to use this chip as a long-term solution? TTBOMK SMI is out
of that business (retail graphics chips) - at least they claimed to be
when we last tried to talk to them a couple of years ago. I would say
that Trident is a better choice for future production.

By the way, have you considered one of the other Epson parts, e.g.
SED1386, which can support CRT or LCD? Or do you need dual-head
operation with different outputs on CRT and LCD?


    Reply to author    Forward  
You must Sign in before you can post messages.
To post a message, you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Ted Schroeder  
View profile   Translate to Translated (View Original)
 More options 14 Apr 2004, 17:08
Newsgroups: comp.os.linux.development.system, comp.os.linux.development, comp.os.linux.hardware
From: Ted Schroeder <t...@schroeder.net>
Date: Wed, 14 Apr 2004 09:08:26 -0700
Local: Wed 14 Apr 2004 17:08
Subject: Re: Silicon Motion 712 (Lynx EM+) and AMD Alchemy
Reply to author | Forward | Print | Individual message | Show original | Report this message | Find messages by this author
Thanks for the response:

Lewin A.R.W. Edwards wrote:
>>fine, except the Epson doesn't have enough memory bandwidth to drive both and
>>LCD and a CRT display at the same time which is a requirement of this
>>1) Can I just use the VESA frame buffer driver with this setup? (That is, VESA
>>claims to be x86 only, but will it work in this setup?)

> The question is kind of bass-ackwards. The VESA framebuffer driver is
> not really "x86-specific" as such, but the whole idea is predicated on
> the existence of a VESA BIOS in your target system. An extended int
> 10h call is made to set the video mode. If your system doesn't have a
> VESA BIOS extension (which it won't if it's not a vanilla x86 system)
> then the concept of using the VESA driver is meaningless.

Thanks for that tip. I know that X has some int10 simulation stuff in it. I'll
take a closer look at that.

>>2) If not, does a frame buffer driver exist for the SM712 chip?

> There is no direct kernel support for the Lynx series. Are you
> planning to use this chip as a long-term solution? TTBOMK SMI is out
> of that business (retail graphics chips) - at least they claimed to be
> when we last tried to talk to them a couple of years ago. I would say
> that Trident is a better choice for future production.

Hmm. That's news to me. We're finding no problem getting SM712 chips in plenty
of volume for the forseeable future. I will ask our hardware guy about this.

> By the way, have you considered one of the other Epson parts, e.g.
> SED1386, which can support CRT or LCD? Or do you need dual-head
> operation with different outputs on CRT and LCD?

We're using the SED1386 now and it, quite honestly, is not even close to
powerful enough to get the job done. It barely supports 800x600x16 and when you
put it in that mode the memory bandwidth is so limited that we had to reduce the
refresh rate to about 30 Hz to allow the CPU enough access to the VRAM so that
screen paints didn't take several seconds. This same memory bandwidth problem is
the reason why right now we can only output to either the CRT or the LCD. Not
enough bandwidth to make them both run at the same time. In addition, we're
going to 1024x768 size screens which aren't supported at all by the 1386.

Ted


    Reply to author    Forward  
You must Sign in before you can post messages.
To post a message, you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »

Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2009 Google