linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Richard B. Johnson" <root@chaos.analogic.com>
To: Andrew Kirilenko <icedank@gmx.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Searching for string problems
Date: Wed, 23 Apr 2003 13:39:55 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.53.0304231311460.25222@chaos> (raw)
In-Reply-To: <200304231958.43235.icedank@gmx.net>

On Wed, 23 Apr 2003, Andrew Kirilenko wrote:

> Hello!
>
> OK. I've solved my problems with storing data (problem was with improper DS
> setup - thanks to all, pointed me to this). And now I should perform a search
> in the BIOS are for particular string (version of BIOS ). Here is my code
> (it's located in the setup.S, so executes in the real mode, not ptotected).
>
> -->
> start_of_setup:
> 	jmp cl_start
> cl_id_str:      .string "BIOS 0.1"
> cl_start:
>         movb    $0, %al
>         movw    $0xe000, %bx
> cl_compare:
>         incw    %bx
>         movw    %bx, %si
>         cmpw    $0xefff, %si
>         je      cl_compare_done
>         movw    $cl_id_str, %di
> cl_compare_inner:
>         movb    (%di), %ah
>         cmpb    $0, %ah
>         je      cl_compare_done_good
>         cmpb    (%si), %ah
>         jne     cl_compare
>         incw    %si
>         incw    %di
>         jmp     cl_compare_inner
> cl_compare_done_good:
>         movb    $1, %al
> cl_compare_done:
> <--
>
> This code don't work... I'm sure, that's because of inproper registers setup
> (or maybe address range is wrong). Please help me.
>

Hmm, maybe you should just learn assembly off-line.

cl_id_str:      .string "BIOS 0.1"
cl_id_end:

scan:	movw	%cs, %ax	# Get code-segment
	movw	%ax, %ds	# Set into data segment
	movw	%ax, %es	# Set into extra segment CS=ES=DS
	cld			# Compare forwards
	movw	$cl_id_str, %si	# String to compare
	movw	$were_in_the_bios_you_expect_to_find_it, %di
	movw	$cl_id_end, %cx	# Offset to this label
	subw	%si, %cx	# CX = length of string
	decw	%cx		# Don't compare \0
	repz	cmpsb		# Continue as long as they compare
	jz	found		# String was found
				# Not found here
found:

If you need to search the whole BIOS for that string, you need to
set up an outer loop using an unused register which starts at
the offset of the BIOS and increments by one byte everytime
you can't find the string. This value gets put into %di, instead
of the absolute number specified above.

Like:

scan:	movw	%cs, %ax
	movw	%ax, %ds
	movw	%ax, %es
	movw	$where_in_BIOS_to_start, %bx
	cld
1:	movw	$cl_id_str, %si		# Offset of search string
	movw	$cl_id_end, %cx		# Offset of string end + 1
	subw	%si, %cx		# String length
	decw	%cx			# Don't look for the \0
	movw	%bx, %di		# ES:DI = where to look
	repz	cmpsb			# Loop while the same
	jz	found			# Found the string
	incb	%bx			# Next starting offset
	cmpb	$_BIOS_END, %bx		# Check for limit
	jb	1b			# Continue
never_found_anywhere:

found:


Note that the `gas` .string macro puts in a '\0', assuming it's
a 'C' string. You don't want to put that in the comparison. That's
why you search one-less than the allocation length. There are
predefined macros available for 'len', also.


Cheers,
Dick Johnson
Penguin : Linux version 2.4.20 on an i686 machine (797.90 BogoMips).
Why is the government concerned about the lunatic fringe? Think about it.


  reply	other threads:[~2003-04-23 17:25 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-23 16:58 Searching for string problems Andrew Kirilenko
2003-04-23 17:39 ` Richard B. Johnson [this message]
2003-04-23 18:05   ` Andrew Kirilenko
2003-04-23 18:15     ` Richard B. Johnson
2003-04-23 18:25       ` Andrew Kirilenko
2003-04-23 18:56         ` Richard B. Johnson
2003-04-23 19:00           ` Andrew Kirilenko
2003-04-23 19:11             ` Randy.Dunlap
2003-04-23 19:37             ` Richard B. Johnson
2003-04-23 19:48               ` Andrew Kirilenko
2003-04-23 20:05                 ` Randy.Dunlap
2003-04-23 20:05                 ` Richard B. Johnson
2003-04-23 20:12                   ` Andrew Kirilenko
2003-04-23 18:59         ` Randy.Dunlap

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=Pine.LNX.4.53.0304231311460.25222@chaos \
    --to=root@chaos.analogic.com \
    --cc=icedank@gmx.net \
    --cc=linux-kernel@vger.kernel.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 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).