From: Vladimir 'phcoder' Serbinenko <phcoder@gmail.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: success booting hdt.c32 module with memdisk
Date: Fri, 30 Oct 2009 20:54:28 +0100 [thread overview]
Message-ID: <4AEB4474.7010801@gmail.com> (raw)
In-Reply-To: <20091029220121.792a3ce2@shiva.selfip.org>
J. Bakshi wrote:
> On Thu, 29 Oct 2009 16:41:17 +0100
> Vladimir 'phcoder' Serbinenko <phcoder@gmail.com> wrote:
>
>
>> Hello
>> J. Bakshi wrote:
>>
>>> Hello list,
>>>
>>> Finally I got success booting hdt.c32 module ( hdt = hardware
>>> detection tool) with the latest floppy image released by hdt team.
>>> hdt.c32 is a syslinux module. As per their suggestion the following
>>> config works for me from usb stick.
>>>
>>> menuentry HDT {
>>> linux16 /memdisk
>>> initrd16 /<hdt_floppy_image>
>>> }
>>>
>>> Though it would be nice to see grub's power to directly load
>>> syslinux module like this one :-)
>>>
>>>
>>>
>> I would be happy to have syslinux com32 glue level. Are you willing to
>> code one?
>>
>
> I would Love to do so but as a Linux sysadmin my programming knowledge is restricted in shell-script :-(
> If you permit me and show me the direction then I can ask the required info at hdt group.
>
>
Basically you just need to get coding
1) Verify that the module is under compatible license
2) Put it into grub2 directory and add to rmk file
3) Fix all compile errors
Binary compatibility is more difficult to get binary compatibility but
is probably useless too as anyway you can't have non GPLv3+-compatible
modules so source compatibility is enough. Additionally having them as
source in grub-extras potentially makes it useful on non-pc as well
--
Regards
Vladimir 'phcoder' Serbinenko
Personal git repository: http://repo.or.cz/w/grub2/phcoder.git
next prev parent reply other threads:[~2009-10-30 19:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-29 14:50 success booting hdt.c32 module with memdisk J. Bakshi
2009-10-29 15:41 ` Vladimir 'phcoder' Serbinenko
2009-10-29 16:31 ` J. Bakshi
2009-10-30 19:54 ` Vladimir 'phcoder' Serbinenko [this message]
2009-10-31 4:37 ` J. Bakshi
2009-10-30 18:41 ` Robert Millan
2009-10-30 19:50 ` Vladimir 'phcoder' Serbinenko
2009-10-30 22:49 ` Robert Millan
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=4AEB4474.7010801@gmail.com \
--to=phcoder@gmail.com \
--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.