linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Antonino A. Daplas" <adaplas@gmail.com>
To: "Antonino A. Daplas" <adaplas@gmail.com>
Cc: vasvir@iit.demokritos.gr, linux-fbdev-devel@lists.sourceforge.net
Subject: Re: Twister savagefb doesn't sync
Date: Sat, 27 May 2006 17:29:31 +0800	[thread overview]
Message-ID: <44781BFB.5020708@gmail.com> (raw)
In-Reply-To: <44781B3A.5030406@gmail.com>

Antonino A. Daplas wrote:
> Vassilis Virvilis wrote:
>> Antonino A. Daplas wrote:
>>
>>> If you can somehow dump the registers of the working and non-working
>>> mode,
>>> we might be able find a pattern.
>>>
>>> If you don't know how to dump the register contents, let me know and I'll
>>> send you a userspace utility to do that.
>>>
>>>
>> I found dumpreg from the svgalib distribution (svgalib-bin in debian).
>> Is this
>> sufficient? 
> 
> It might not be sufficient as it won't be able to recognize savage extended
> VGA registers.
> 
>> If not could you please send me the userspace utility you
>> mentioned
>> the other day?
>>
> 
> Ok, attached, it's a quick hack. Before using it open the file savagedump.c 
> and look for the following defines:
> 
> #define PCI_ID        0x8d04  /* put the PCI id of the device here */
> #define PCI_PBASE     0xdfe80000  /* put the start address of the PCI resource here */
> 
> and replace the above values with your own. First do "lspci -n | grep "Class 0300"
> and you'll get something like this:
> 
> 01:00.0 Class 0300: 5333:8d04
> 
> Use the last 4 digit ID for the PCI_ID (ie 8d04):
> 
> Then do lspci -v -n 5333:8d04 (using instead the vendor:device that you got) and you

Typo.  I meant

lspci -v -d 5333:8d04

Tony


-------------------------------------------------------
All the advantages of Linux Managed Hosting--Without the Cost and Risk!
Fully trained technicians. The highest number of Red Hat certifications in
the hosting industry. Fanatical Support. Click to learn more
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642

  reply	other threads:[~2006-05-27  9:29 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-16  7:46 Twister savagefb doesn't sync Vassilis Virvilis
2006-05-23 18:51 ` Vassilis Virvilis
2006-05-23 21:43   ` Antonino A. Daplas
2006-05-24  4:04     ` Knut Petersen
2006-05-24 11:38       ` Vassilis Virvilis
2006-05-24 11:31     ` Vassilis Virvilis
2006-05-27  7:47     ` Vassilis Virvilis
2006-05-27  9:26       ` Antonino A. Daplas
2006-05-27  9:29         ` Antonino A. Daplas [this message]
2006-05-28 12:16           ` Vassilis Virvilis
2006-05-29  0:13             ` Antonino A. Daplas
2006-05-29 13:22               ` Vassilis Virvilis
2006-05-29 21:00                 ` Antonino A. Daplas
2006-05-31 14:11                   ` Vassilis Virvilis
2006-06-05 16:38                   ` Vassilis Virvilis
2006-06-06  5:11                     ` Alex Deucher
2006-06-06  9:57                       ` Vassilis Virvilis
2006-06-06 14:43                         ` Alex Deucher
2006-06-11 12:03                           ` Twister savagefb doesn't sync (resolved for 640x480@64K) Vassilis Virvilis
2006-06-11 15:03                             ` Alex Deucher
2006-06-12  6:12                               ` Vassilis Virvilis
2006-06-12 14:37                                 ` Alex Deucher
2006-06-12 15:50                                   ` Vassilis Virvilis
2006-06-12  8:33                             ` Geert Uytterhoeven

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=44781BFB.5020708@gmail.com \
    --to=adaplas@gmail.com \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=vasvir@iit.demokritos.gr \
    /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).