linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ferenc Engard <ferenc@engard.hu>
To: linux-kernel@vger.kernel.org
Subject: Geode GX1, video acceleration -> crash
Date: Thu, 3 Jul 2003 18:24:31 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.40.0307031759060.10456-100000@domesticus.fery-local.hu> (raw)

Hello there,

First of all, I am new to the framebuffer business, and looks like
that the linux-fbdev.org site is down. Where can I find a mailing list
or other information resource about framebuffers in general, and about
Geode hardware specifically? It is a nightmare to find any information
for Geode on linux... :((

I am developing a graphical app for an Advantech PCM-5820 (I think :),
i.e. a Geode GX1 / CS5530 board, 64MB RAM, which I want to run a linux
/ framebuffer application on.

Now, about my problem:

I have installed the 2.4.17 kernel, patched with NSC's original Geode
fb driver (nsc-kfb-driver-2.7.7.tar.gz), and compiled it successfully.
Also, as I couldn't find in other places, I have downloaded the
nsc_xfree_2.7.6.tgz package just to compile the GAL library
(nsc_galfns.c) in it, as this was what I needed.

First surprise: I cannot switch into 32bpp modes! Did I miss
something? fbset refuses it, setting at boot time do not work either.

Next, I have written a small application to test the processor's
bitblt capability. The program calls Gal_screen_to_screen_blt() to
scroll a rectangle on the screen, then usleeps a bit. It does work,
although the scheduler do not give back the run to the task until
approx. 20ms elapses (no problem at now), and in 16bpp, it do not
scroll the region but inverses it(?!).  I suppose that it is not good
that the console writes out things while the bitblt engine works.
Question: should I disable writing to the console while my app runs?
How?

But the real problem is, that I wanted to benchmark the system while
the scrolling continues, and issued a
dd if=/dev/mem of=/dev/null bs=1024 count=32768
command. For the second go, the system freezed like a good
refrigerator. No kernel panic, nothing, just freezed. It can be
repeated, if I copy just the 1st MB of RAM, then it freezes for the
5-6th go. :((

What can I do? How to debug?

Please cc your answers to ferenc@engard.hu, too!

Thank you:
Circum


             reply	other threads:[~2003-07-03 16:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-03 16:24 Ferenc Engard [this message]
2003-07-03 19:56 ` Geode GX1, video acceleration -> crash Alan Cox
2003-07-03 22:37 ` NunO fELICIO
2003-07-11 18:10 Keyser Soze
2003-07-11 18:27 ` Alan Cox
2003-07-11 21:10 ` Ferenc Engard
2003-07-12 17:04   ` Jan Rychter

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=Pine.LNX.4.40.0307031759060.10456-100000@domesticus.fery-local.hu \
    --to=ferenc@engard.hu \
    --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 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).