From: Christian Franke <Christian.Franke@t-online.de>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] cdrom access patch
Date: Tue, 11 Mar 2008 22:10:46 +0100 [thread overview]
Message-ID: <47D6F556.9040500@t-online.de> (raw)
In-Reply-To: <ca0f59980803100853h67c73aeh8ffee0552e3fbc78@mail.gmail.com>
Bean wrote:
> ...
>
> After some testing, i think the new version has some compatible issue,
> i remember Christian Franke reports that some bios doesn't support int
> 42 for cdrom, so grub_biosdisk_check_int13_extensions will fail. Would
> someone check if func 4b01 (the first patch cd.diff) works in such
> situation ?
>
>
cd.diff works on this specific PC (Asus A8N, Phonix-Award BIOS), CD
appears as hd31.
BTW: grub_biosdisk_iterate should IMO always expose the boot_drive (see
my latest patch).
With current CVS and cd.diff, the boot_drive would not be visible in
'ls' if e.g 0x80=HDD, 0x82=boot CD (as seen on some old Laptop).
Christian
next prev parent reply other threads:[~2008-03-11 21:11 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-05 8:49 [PATCH] cdrom access patch Bean
2008-03-07 15:37 ` Vesa Jääskeläinen
2008-03-09 15:33 ` Bean
2008-03-10 15:53 ` Bean
2008-03-11 21:10 ` Christian Franke [this message]
2008-03-12 5:26 ` Bean
2008-03-12 6:52 ` Christian Franke
2008-03-13 22:59 ` Christian Franke
2008-03-14 5:33 ` Bean
2008-03-14 17:28 ` Pavel Roskin
2008-03-14 19:58 ` Bean
2008-03-14 20:56 ` Bean
2008-03-14 20:58 ` Vesa Jääskeläinen
2008-03-15 7:34 ` Bean
2008-03-15 8:49 ` Vesa Jääskeläinen
2008-03-15 10:54 ` Bean
2008-03-15 19:01 ` Christian Franke
2008-03-17 4:31 ` Pavel Roskin
2008-03-17 6:21 ` Bean
2008-03-19 22:09 ` Pavel Roskin
2008-03-20 6:06 ` Bean
2008-03-24 4:15 ` Bean
2008-03-14 23:20 ` Christian Franke
-- strict thread matches above, loose matches on Subject: below --
2008-03-06 23:58 Kalamatee
2008-03-08 20:16 Kalamatee
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=47D6F556.9040500@t-online.de \
--to=christian.franke@t-online.de \
--cc=grub-devel@gnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.