From: David Woodhouse <dwmw2-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
To: Pavel Machek <pavel-AlSwsSmVLrQ@public.gmane.org>
Cc: Bjorn Wesen <bjorn.wesen-VrBV9hrLPhE@public.gmane.org>,
Ducrot Bruno <ducrot-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>,
ACPI mailing list
<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: [PATCH] s3_bios and lcall $0xc000,$3
Date: 18 Feb 2003 16:56:47 +0000 [thread overview]
Message-ID: <1045587407.2231.2.camel@passion.cambridge.redhat.com> (raw)
In-Reply-To: <20030218111954.GB5277-jyMamyUUXNJG4ohzP4jBZS1Fcj925eT/@public.gmane.org>
On Tue, 2003-02-18 at 11:19, Pavel Machek wrote:
> > It seems pretty bleak since for example the reason I needed s3_bios on the
> > travelmate was because the TFT did not want to come on by just doing the int
> > 0x10h call or the VESA set video mode call. Some other magic was needed
> > which apparently the lcall did. And we can't really have specific VGA wakeup
> > codes for every possible card or laptop.. I tried searching the ralph brown
> > irq list for that lcall but could not find any - what documentation did you
> > dig up this magic call from ? :))
>
> Its call bios uses to initialize video roms. It really should be in
> interrupt list somewhere. [Someone helped me with that].
Not just video ROMS -- it's the way the BIOS handles _all_ BIOS
extensions -- SCSI drivers, network boot roms, etc. It scans from
0xC0000 up to 0xE0000 in steps of (IIRC) 0x2000, checking for a
'0x55 0xaa' signature and jumping to offset 0003 in the relevant segment
if it finds such. Your video BIOS generally lives at segment 0xC000, and
when run it will initialise the hardware and install itself on the INT
10h vector for later use.
--
dwmw2
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
next prev parent reply other threads:[~2003-02-18 16:56 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-17 15:38 s3_bios and lcall $0xc000,$3 Bjorn Wesen
[not found] ` <Pine.LNX.4.33.0302171423290.21415-100000-Hi2dXqvvzfEtpH44vsTDoQ@public.gmane.org>
2003-02-17 15:53 ` [PATCH] " Bjorn Wesen
[not found] ` <Pine.LNX.4.33.0302171647410.21415-100000-Hi2dXqvvzfEtpH44vsTDoQ@public.gmane.org>
2003-02-17 17:16 ` Ducrot Bruno
[not found] ` <20030217171610.GC25625-j6u/t2rXLliUoIHC/UFpr9i2O/JbrIOy@public.gmane.org>
2003-02-17 18:13 ` Nigel Cunningham
[not found] ` <1045505626.5596.20.camel-udXHSmD1qAz9bBlWBkG5g4WQyAnV0byH@public.gmane.org>
2003-02-17 23:55 ` Pavel Machek
[not found] ` <20030217235512.GA7372-jyMamyUUXNJG4ohzP4jBZS1Fcj925eT/@public.gmane.org>
2003-02-18 1:42 ` Nigel Cunningham
[not found] ` <1045532563.2161.9.camel-udXHSmD1qAz9bBlWBkG5g4WQyAnV0byH@public.gmane.org>
2003-02-18 2:09 ` Nigel Cunningham
[not found] ` <1045534117.3556.12.camel-udXHSmD1qAz9bBlWBkG5g4WQyAnV0byH@public.gmane.org>
2003-02-18 11:21 ` Pavel Machek
2003-02-18 0:02 ` Pavel Machek
[not found] ` <20030218000206.GC7372-jyMamyUUXNJG4ohzP4jBZS1Fcj925eT/@public.gmane.org>
2003-02-18 1:22 ` Bjorn Wesen
[not found] ` <Pine.LNX.4.33.0302180216520.21776-100000-Hi2dXqvvzfEtpH44vsTDoQ@public.gmane.org>
2003-02-18 11:19 ` Pavel Machek
[not found] ` <20030218111954.GB5277-jyMamyUUXNJG4ohzP4jBZS1Fcj925eT/@public.gmane.org>
2003-02-18 12:40 ` Charl P. Botha
[not found] ` <1045572005.7077.40.camel-1Jw6Eky0yc0@public.gmane.org>
2003-02-18 13:29 ` Bjorn Wesen
[not found] ` <Pine.LNX.4.33.0302181426010.22900-100000-Hi2dXqvvzfEtpH44vsTDoQ@public.gmane.org>
2003-02-18 13:56 ` Charl P. Botha
2003-02-18 16:31 ` Patrick Mochel
2003-02-18 16:08 ` Pavel Machek
2003-02-18 16:56 ` David Woodhouse [this message]
2003-02-18 13:32 ` Bjorn Wesen
2003-02-17 18:06 ` Alan Cox
2003-02-17 18:19 ` Ducrot Bruno
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=1045587407.2231.2.camel@passion.cambridge.redhat.com \
--to=dwmw2-wegcikhe2lqwvfeawa7xhq@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=bjorn.wesen-VrBV9hrLPhE@public.gmane.org \
--cc=ducrot-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org \
--cc=pavel-AlSwsSmVLrQ@public.gmane.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