From owner-freebsd-mobile Tue Jul 24 14:20:44 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from smtp.whitebarn.com (Spin.whitebarn.com [216.0.13.113]) by hub.freebsd.org (Postfix) with ESMTP id 7C1BA37B401; Tue, 24 Jul 2001 14:20:40 -0700 (PDT) (envelope-from Bob@Talarian.Com) Received: from Talarian.Com (NewStorm.whitebarn.com [216.0.13.77]) by smtp.whitebarn.com (8.9.3/8.9.3) with ESMTP id QAA59054; Tue, 24 Jul 2001 16:20:38 -0500 (CDT) (envelope-from Bob@Talarian.Com) Message-ID: <3B5DE5AD.5050202@Talarian.Com> Date: Tue, 24 Jul 2001 16:16:29 -0500 From: Bob Van Valzah User-Agent: Mozilla/5.0 (X11; U; Linux i386; en-US; rv:0.9.2) Gecko/20010628 X-Accept-Language: en-us MIME-Version: 1.0 To: John Baldwin , Doug Ambrisko Cc: FreeBSD-Mobile@FreeBSD.org Subject: Re: ThinkPad 600X: Can't work out which disk we are booting from References: Content-Type: multipart/alternative; boundary="------------010709050307080902030300" Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org --------------010709050307080902030300 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Doug, Glad you're aware of the problem and have already formulated a fix. John, I agree that the header file approach might be cleaner. But here's another idea: Could the "jmp main" at the start of boot1.s be followed immediately by a "jmp xread"? This'd create a sort of entry point table at the start of boot1 that could be used by boot2 without fear of things moving around. But I have to say that I haven't written any substantial amounts of assembler since the 8080 days (dating myself there) and I've never looked at the x86 boot sequence, so I may be way out of my league with this suggestion. Bob John Baldwin wrote: >On 24-Jul-01 Doug Ambrisko wrote: > >>Note this is fixed via pr-26382. Which makes IBM ThinkPads & Desktops >>boot from a FreeBSD bootable CD. The problem is they expect to see >>a "MS-DOS" type disk header which {Open,Net}BSD and Linux have so things >>work. FreeBSD does not. I made an 4.3 ISO image with this patch applied >>to the boot code. Some people on this list have access to that. I did >>that at my former employer (IBM) they might be able to send you the >>ISO image. Yes it is a pain on some IBM machine in which it is difficult >>to have a floppy and CD device attached at the same time. >> > >Robert Nordier has dropped maintainership of the x86 boot blocks, so I'll try >and look at this PR today or next week. Keep reminding me if I don't get >around to it. :) Hmm, could you update the patch so instead of patching boot2 >you add a new header file that defines the offset of xread and have that header >file have a dependecy on ${.OBJDIR}/boot1 and be generated from boot1? I >think that would be cleaner than patching actual soure code. > --------------010709050307080902030300 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit Doug, Glad you're aware of the problem and have already formulated a fix.

John, I agree that the header file approach might be cleaner.

But here's another idea: Could the "jmp main" at the start of boot1.s be followed immediately by a "jmp xread"? This'd create a sort of entry point table at the start of boot1 that could be used by boot2 without fear of things moving around. But I have to say that I haven't written any substantial amounts of assembler since the 8080 days (dating myself there) and I've never looked at the x86 boot sequence, so I may be way out of my league with this suggestion.

    Bob

John Baldwin wrote:
On 24-Jul-01 Doug Ambrisko wrote:
Note this is fixed via pr-26382.  Which makes IBM ThinkPads & Desktops
boot from a FreeBSD bootable CD. The problem is they expect to see
a "MS-DOS" type disk header which {Open,Net}BSD and Linux have so things
work. FreeBSD does not. I made an 4.3 ISO image with this patch applied
to the boot code. Some people on this list have access to that. I did
that at my former employer (IBM) they might be able to send you the
ISO image. Yes it is a pain on some IBM machine in which it is difficult
to have a floppy and CD device attached at the same time.

Robert Nordier has dropped maintainership of the x86 boot blocks, so I'll try
and look at this PR today or next week. Keep reminding me if I don't get
around to it. :) Hmm, could you update the patch so instead of patching boot2
you add a new header file that defines the offset of xread and have that header
file have a dependecy on ${.OBJDIR}/boot1 and be generated from boot1? I
think that would be cleaner than patching actual soure code.


--------------010709050307080902030300-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message