All of lore.kernel.org
 help / color / mirror / Atom feed
From: Knut Petersen <Knut_Petersen@t-online.de>
To: "'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Cc: jani@iv.ro, jani@astechnix.ro
Subject: tridentfb 2.6.0* broken for VIA integrated graphics core on EPIA Mini-ITX boards
Date: Fri, 24 Oct 2003 09:25:26 +0200	[thread overview]
Message-ID: <3F98D3E6.60202@t-online.de> (raw)

Hi everybody,

tridentfb stopped working on an EPIA Mini-ITX boards (VIA Eden cpu,  VIA 
8601A
North Bridge, VT 8231 South Bridge).

SuSE kernel 2.4.20 reports:

Oct 24 08:27:04 epia kernel: tridentfb: Trident framebuffer 0.7.5 
initializing
Oct 24 08:27:04 epia kernel: tridentfb: framebuffer size = 8192 Kb
Oct 24 08:27:04 epia kernel: tridentfb: Trident Microsystems 
CyberBlade/i1 board found
Oct 24 08:27:04 epia kernel: Console: switching to colour frame buffer 
device 80x25
Oct 24 08:27:04 epia kernel: tridentfb: fb0: Trident frame buffer device 
640x400-8bpp

tridentfb of 2.4.20 works fine.



Kernel 2.6.0-test8-bk3 reports:

Oct 24 08:25:24 linux kernel: tridentfb: Trident framebuffer 
0.7.8-NEWAPI initializing
Oct 24 08:25:24 linux kernel: tridentfb: framebuffer size = 8192 Kb
Oct 24 08:25:24 linux kernel: tridentfb: 0000:01:00.0 board found
Oct 24 08:25:24 linux kernel: tridentfb: probe of 0000:01:00.0 failed 
with error -22

No difference if compiled as a module or compiled directly into kernel.
Vesafb is usable but slow.

Any ideas?

cu
 Knut


             reply	other threads:[~2003-10-24  7:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-24  7:25 Knut Petersen [this message]
2003-10-24  7:28 ` tridentfb 2.6.0* broken for VIA integrated graphics core on EPIA Mini-ITX boards Jani Monoses

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=3F98D3E6.60202@t-online.de \
    --to=knut_petersen@t-online.de \
    --cc=jani@astechnix.ro \
    --cc=jani@iv.ro \
    --cc=linux-kernel@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.