mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Randy.Dunlap" <rddunlap@osdl.org>
To: "Thomas S. Iversen" <zensonic@zensonic.dk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Help with debugging of a framebuffer driver on a legacyfree system.
Date: Wed, 27 Aug 2003 08:22:38 -0700	[thread overview]
Message-ID: <20030827082238.0508aa9e.rddunlap@osdl.org> (raw)
In-Reply-To: <20030827142035.GA25937@zensonic.dk>

On Wed, 27 Aug 2003 16:20:35 +0200 "Thomas S. Iversen" <zensonic@zensonic.dk> wrote:

| Hi there 
| 
| As part of a project I am trying to write a framebuffer device
| driver for a graphic chip. Up until now I have compiled my
| code as a module and been doing insmod, rmmod and that have worked
| nicely.
| 
| I then tried to compile the driver into the kernel but that
| makes the kernel hang. As my development system are a legacy
| free laptop and my driver initializes the screen, the kernel
| hangs without me being able to figure out where and why that
| happend.

First choice would be to develop on a system where you can add
(PCI?) bus probes or other adapters/gadgets, like a port-80 card.

| So I seek advice on how to debug the driver! As said, the
| laptop are legacy free, so I have not got a serial port. 
| I have tried a usb->serial adapter, but that requires a driver.
| Can I do USB->USB on another computer? Or?
| 
| Or am I stuck with coding my own printk variant and writing to the
| screen or is there any other option I have not thought of?

There are already early_printk patches and an x86-specific
"poke a character into video RAM" patch.  The latter one is at:
  http://kernelnewbies.org/documents/videochar.txt

--
~Randy

      reply	other threads:[~2003-08-27 15:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-27 14:20 Thomas S. Iversen
2003-08-27 15:22 ` Randy.Dunlap [this message]

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=20030827082238.0508aa9e.rddunlap@osdl.org \
    --to=rddunlap@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zensonic@zensonic.dk \
    /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

all inboxes | Powered by JetHome®