From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] SED13806 and MPC866
Date: Wed, 06 Aug 2003 08:47:26 +0200 [thread overview]
Message-ID: <20030806064731.E7672C59E4@atlas.denx.de> (raw)
In-Reply-To: Your message of "Wed, 06 Aug 2003 08:29:21 +0200." <MFEGIPJEFHIKHGDLDACIGEOJCAAA.marco.schramel@go.bartec.de>
Dear Marco,
in message <MFEGIPJEFHIKHGDLDACIGEOJCAAA.marco.schramel@go.bartec.de> you wrote:
>
> Such devices like my EPSON controller are a not kernel specificly.
> Will it be used like a normal device with a device driver ???
This depends on the implementation. Often you will find some device
driver provided by the chip manufacturer (or some other third
parties). And often this driver will provide a standard framebuffer
interface.
> My kernel config has no option for a EPSON graphic controller, i think.
It might have one after adding the driver to your kernel source tree :-)
> Where do the embedded Linux store the parameters which was given by u-boot?
Parameters are passed in registers plus some data structure in RAM.
How and where Linux stores this information depends on a couple of
things, like processor architecture and kernel version.
Why do you ask?
[Maybe we should move this discussion into a Linux group?]
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd at denx.de
Yes, it is written. Good shall always destroy evil.
-- Sirah the Yang, "The Omega Glory", stardate unknown
prev parent reply other threads:[~2003-08-06 6:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-05 12:28 [U-Boot-Users] SED13806 and MPC866 Marco Schramel
2003-08-05 12:40 ` Wolfgang Denk
2003-08-05 13:31 ` AW: " Marco Schramel
2003-08-05 14:38 ` Wolfgang Denk
2003-08-06 6:29 ` Marco Schramel
2003-08-06 6:47 ` Wolfgang Denk [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=20030806064731.E7672C59E4@atlas.denx.de \
--to=wd@denx.de \
--cc=u-boot@lists.denx.de \
/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