From: phcoder <phcoder@gmail.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: GRUB2 - Please add support for 64-bit FreeBSD
Date: Sun, 12 Apr 2009 15:18:42 +0200 [thread overview]
Message-ID: <49E1EA32.1020004@gmail.com> (raw)
In-Reply-To: <49E08411.70306@gmail.com>
I have looked in it and isolated the files which changes are needed:
1) switching to x86_64 mode and setting the paging up
2) elf64 parser
3) different boot parameters
I'm quite optimistic and think I should have working freebsd64 soon.
Another good piece of news is that it seems that in freebsd64 all BIOS
calls are moved to bootloader. It's a very wise decision which also
allows FreeBSD64 to boot on EFI or coreboot
phcoder wrote:
> I haven't looked in depth yet, but it's a bit more. the loader switches
> to amd64 and sets preliminary page translation
> Bean wrote:
>> On Sat, Apr 11, 2009 at 5:54 AM, Daniel Nebdal <dnebdal@gmail.com> wrote:
>>> Bean wrote:
>>>> Hi,
>>>>
>>>> Please try the btx loader in /boot/loader, which I believe to be
>>>> 32-bit even in amd64 freebsd. The btx loader is an a.out executable,
>>>> grurb2 has supported for it already.
>>> Ah, just noticed I replied to this before subscribing, so the copy to
>>> the list bounced.
>>> Let's try again.
>>>
>>> The BTX loader starts, yes - but the reason I'm using GRUB2 in the
>>> first place is to skip it,
>>> since it doesn't seem to support logical partitions.
>>
>> Hi,
>>
>> Oh, thanks for the information. The 32-bit bsd kernel is basically an
>> elf image that needs a little address translation:
>>
>> physical address = virtual address & 0xFFFFFF
>>
>> I think the principle can be applied to 64-bit kernel as well, it
>> shouldn't be difficult to add support for it.
>>
>
>
--
Regards
Vladimir 'phcoder' Serbinenko
next prev parent reply other threads:[~2009-04-12 13:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-10 21:54 GRUB2 - Please add support for 64-bit FreeBSD Daniel Nebdal
2009-04-11 7:37 ` Bean
2009-04-11 7:56 ` Chip Panarchy
2009-04-11 11:50 ` phcoder
2009-04-11 23:44 ` Chip Panarchy
2009-04-12 13:18 ` phcoder [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-04-08 4:08 Chip Panarchy
2009-04-08 7:07 ` Bean
2009-04-08 7:16 ` phcoder
2009-04-09 23:06 ` Joey Korkames
2009-04-09 23:20 ` phcoder
2009-04-09 23:30 ` Joey Korkames
2009-04-09 23:39 ` Yoshinori K. Okuji
2009-04-10 0:51 ` Chip Panarchy
2009-04-10 4:58 ` Bean
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=49E1EA32.1020004@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.