From: Nikunj A Dadhania <nikunj@linux.vnet.ibm.com>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, thuth@redhat.com, aik@ozlabs.ru,
dvaleev@suse.com
Subject: Re: [PATCH SLOF 3/5] disk-label: introduce helper to check fat filesystem
Date: Tue, 23 Jun 2015 11:36:24 +0530 [thread overview]
Message-ID: <87fv5jdkm7.fsf@linux.vnet.ibm.com> (raw)
In-Reply-To: <20150622193555.GD19845@gate.crashing.org>
Hi Segher,
Segher Boessenkool <segher@kernel.crashing.org> writes:
> On Mon, Jun 22, 2015 at 01:29:45PM +0530, Nikunj A Dadhania wrote:
>> +: has-fat-filesystem ( block -- true | false )
>> + \ block 0 byte 0-2 is a jump instruction in all FAT
>> + \ filesystems.
>
> "block" there is not a block number, just a host address. So it's not
> a good name. Maybe do a better name for this word as well, something
> saying it looks at a disk block.
Sure.
>
>> + \ e9 and eb are jump instructions in x86 assembler.
>> + dup c@ e9 <> IF
>> + dup c@ eb <> swap
>> + 2+ c@ 90 <> or
>> + IF false EXIT THEN
>> + ELSE DROP THEN
>> + TRUE
>> +;
>
> Don't write DROP and TRUE in caps please. The purpose of having the
> structure words in caps is to make them stand out more, to make things
> more readable; putting other things in caps as well destroys that.
Sure, will take care.
> Since you factored this, it becomes more readable if you invert the
> conditions:
Sure.
> : fat-bootblock? ( addr -- flag )
> \ byte 0-2 of the bootblock is a jump instruction in
> \ all FAT filesystems.
> \ e9 and eb are jump instructions in x86 assembler.
> dup c@ e9 = IF drop true EXIT THEN
> dup c@ eb = swap 2+ c@ 90 = and ;
>
> (not tested, etc.)
Will test.
Regards,
Nikunj
next prev parent reply other threads:[~2015-06-23 6:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-22 7:59 [PATCH SLOF 0/5] GPT fixes/cleanup and LVM support with FAT Nikunj A Dadhania
2015-06-22 7:59 ` [PATCH SLOF 1/5] disk-label: simplify gpt-prep-partition? routine Nikunj A Dadhania
2015-06-23 7:08 ` Thomas Huth
2015-06-22 7:59 ` [PATCH SLOF 2/5] introduce 8-byte LE helpers Nikunj A Dadhania
2015-06-23 7:09 ` Thomas Huth
2015-06-22 7:59 ` [PATCH SLOF 3/5] disk-label: introduce helper to check fat filesystem Nikunj A Dadhania
2015-06-22 19:35 ` Segher Boessenkool
2015-06-23 6:06 ` Nikunj A Dadhania [this message]
2015-06-22 7:59 ` [PATCH SLOF 4/5] disk-label: add support for booting from GPT FAT partition Nikunj A Dadhania
2015-06-23 7:34 ` Thomas Huth
2015-06-24 2:10 ` Segher Boessenkool
2015-06-24 5:29 ` Nikunj A Dadhania
2015-06-24 5:33 ` Nikunj A Dadhania
2015-06-22 7:59 ` [PATCH SLOF 5/5] disk-label: make gpt detection code more robust Nikunj A Dadhania
2015-06-23 7:46 ` Thomas Huth
2015-06-24 5:34 ` Nikunj A Dadhania
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=87fv5jdkm7.fsf@linux.vnet.ibm.com \
--to=nikunj@linux.vnet.ibm.com \
--cc=aik@ozlabs.ru \
--cc=dvaleev@suse.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=segher@kernel.crashing.org \
--cc=thuth@redhat.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).