Hi!
> > Then how does 1.44 megabytes of data from a floppy disk (that won't
> > fit below 1 megabyte), that is accessed in real-mode, ever get to
> > above 1 megabyte where it can be decompressed?
>
> The limit is about 508K of compressed image with the floppy boot.
Wrong. 0xe is limit for
On Saturday 30 June 2001 08:47, Pavel Machek wrote:
> Hi!
>
> > > 1.3 Type 'apm -s'
> > > The machine should standby
> > >
> > > 1.4 Wake it and type 'apm -S'
> > > The machine should suspend
> >
> > According to the man pages, "apm -s" does a suspend and "apm -S" does a
> > standb
Hi!
> > 1.3 Type 'apm -s'
> > The machine should standby
> >
> > 1.4 Wake it and type 'apm -S'
> > The machine should suspend
>
> According to the man pages, "apm -s" does a suspend and "apm -S" does a
> standby.
No, original seems good.
apm -s: suspend to ram
apm -S: suspend to disk
** Reply to message from Eric W. Biederman <[EMAIL PROTECTED]> on 23 Jun
2001 14:26:32 -0600
> Pretty decent. It misses a lot of hardware details that we still
> depend on the BIOS to reliably setup for us.
You're right, it does. I think that information should be added. It's a way
for BIOS
Alan Cox wrote:
>
> Linux 2.4 BIOS usage reference
>
> Boot Sequence
> -
>
> Linux is normally loaded either directly as a bootable floppy image or from
> hard disk via a boot loader called lilo. The kernel image is transferred
> into low memory and a parameter block above it.
>
>
Hi Alan.
Brief critique...
> Linux 2.4 BIOS usage reference
> Boot Sequence
> -
>
> Linux is normally loaded either directly as a bootable floppy
> image or from hard disk via a boot loader called lilo. The
> kernel image is transferred into low memory and a parameter
> bloc
On Friday 22 June 2001 12:20, Alan Cox wrote:
> int 0x10 service 3 is used during the boot loading sequence to obtain the
> cursor position. int 0x10 service 13 is used to display loading messages
> as the loading procedure continues. int 0x10 AH=0xE is used to display a
> progress bar of '=' cha
Alan Cox <[EMAIL PROTECTED]> writes:
> Linux 2.4 BIOS usage reference
Pretty decent. It misses a lot of hardware details that we still
depend on the BIOS to reliably setup for us.
I've got code that does all of this so, setup on a couple of
boards so it should just be a matter of tracking it d
> lilo
> grub
> syslinux
> XFree86 (using virtual-8088 to run a video BIOS for a second card?)
Also for monitor identification
> dosemu?
> loadlin?
loadlin does. Dosemu can. It depends how it is configured
The Red Hat installer uses LRMI to do monitor identification by BIOS calls
too. I've not
> It's in arch/i386/boot/setup.S, after label bootsect_second. It's only
> used with bzImage kernels and the floppy bootsector.
I stand corrected. I will add this to the documentation
Alan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EM
> Then how does 1.44 megabytes of data from a floppy disk (that won't
> fit below 1 megabyte), that is accessed in real-mode, ever get to
> above 1 megabyte where it can be decompressed?
The limit is about 508K of compressed image with the floppy boot.
> I think LILO copies each buffer read from
Alan Cox writes:
> [somebody]
>> I could not find any reference to BIOS int 0x15, function 0x87,
>> block-move, used to copy the kernel to above the 1 megabyte
>> real-mode boundary. I think this is still used.
>
> I dont think the kernel has ever used it. The path has always been to
> enter 32bi
Followup to: <[EMAIL PROTECTED]>
By author:"Richard B. Johnson" <[EMAIL PROTECTED]>
In newsgroup: linux.dev.kernel
>
> On Fri, 22 Jun 2001, Alan Cox wrote:
>
> > > I could not find any reference to BIOS int 0x15, function 0x87, block-
> > > move, used to copy the kernel to above the 1 megaby
Typo?
> If the E820 call fails then the INT 15 AX=0xE801 service is called and the
> results are sanity checked. In particular the code zeroes the CX/DX return
>
> values in order to detect BIOS implementations that do not set them
> usable memory data. It also handles older BIOSes that return
Alan Cox wrote:
>
> > I could not find any reference to BIOS int 0x15, function 0x87, block-
> > move, used to copy the kernel to above the 1 megabyte real-mode
> > boundary. I think this is still used.
>
> I dont think the kernel has ever used it. The path has always been to enter
> 32bit mode
On Fri, 22 Jun 2001, Alan Cox wrote:
> > I could not find any reference to BIOS int 0x15, function 0x87, block-
> > move, used to copy the kernel to above the 1 megabyte real-mode
> > boundary. I think this is still used.
>
> I dont think the kernel has ever used it. The path has always been to
> Didn't you disable DMI scan recently, in favor of userspace
> DMI tools?
No. We still scan it but we dont print the stuff out
> > should probably provide the $PIR table, even if it does not
> > provide non ACPI versions of other services.
>
> Sorry, legacy-free => ACPI, certainly not a $PIR
> You've described a relatively complicated procedure well in this document.
> My only suggestion would be to reference the applicable source code files
> throughout the text, so that it's easy to find the associated code.
Thats a good idea . I'll fix that one up
Thanks to all the folks who sent
> I could not find any reference to BIOS int 0x15, function 0x87, block-
> move, used to copy the kernel to above the 1 megabyte real-mode
> boundary. I think this is still used.
I dont think the kernel has ever used it. The path has always been to enter
32bit mode then relocate/uncompress the ke
Looks somewhat familiar. 8;)
(compare http://rddunlap.home.att.net/linit/lin240_init_x86.html) (blatant
plug)
Some comments below.
> -Original Message-
> From: Alan Cox [mailto:[EMAIL PROTECTED]]
> Linux 2.4 BIOS usage reference
>
>
> Boot Sequence
> -
>
...
>
> int 0x
On Fri, 22 Jun 2001, Schilling, Richard wrote:
>
> You've described a relatively complicated procedure well in this document.
> My only suggestion would be to reference the applicable source code files
> throughout the text, so that it's easy to find the associated code.
>
I could not find any
ted Health Services
Mount Vernon, WA USA
http://www.affiliatedhealth.org
phone: 360.856.7129
> -Original Message-
> From: Alan Cox [mailto:[EMAIL PROTECTED]]
> Sent: Friday, June 22, 2001 9:21 AM
> To: [EMAIL PROTECTED]
> Subject: For comment: draft BIOS use document for the ke
> 1.3 Type 'apm -s'
> The machine should standby
>
> 1.4 Wake it and type 'apm -S'
> The machine should suspend
According to the man pages, "apm -s" does a suspend and "apm -S" does a
standby.
--
Brad Pepers
[EMAIL PROTECTED]
-
To unsubscribe from this list: send the line "unsu
** Reply to message from Alan Cox <[EMAIL PROTECTED]> on Fri, 22 Jun
2001 17:20:33 +0100 (BST)
> Firstly a call is made to BIOS INT 15 AX=0xE820 in order to read the
> E820 map. A maximum of 32 blocks are supported by current kernels. The
> 'SMAP' signature is required and tested. In addition t
Linux 2.4 BIOS usage reference
Boot Sequence
-
Linux is normally loaded either directly as a bootable floppy image or from
hard disk via a boot loader called lilo. The kernel image is transferred
into low memory and a parameter block above it.
When booting from floppy disk the B
25 matches
Mail list logo
