From: "Randy.Dunlap" <rddunlap@osdl.org>
To: root@chaos.analogic.com
Cc: icedank@gmx.net, linux-kernel@vger.kernel.org
Subject: Re: Stored data missed in setup.S
Date: Wed, 23 Apr 2003 07:51:58 -0700 [thread overview]
Message-ID: <20030423075158.510e25d2.rddunlap@osdl.org> (raw)
In-Reply-To: <Pine.LNX.4.53.0304231028270.23276@chaos>
On Wed, 23 Apr 2003 10:36:55 -0400 (EDT) "Richard B. Johnson" <root@chaos.analogic.com> wrote:
| On Wed, 23 Apr 2003, Andrew Kirilenko wrote:
|
| [SNIPPED...]
|
| > OK. And now code looks like:
| > -->
| > start_of_setup: # line 160
| > # bla bla bla - some checking code
| > movb $1, %al
| > movb %al, (0x100)
| > ....
| > ....
| > cmpb $1, (0x100)
| > je bail820 # and it DON'T jump here
| > <--
| >
|
| > I'm sure, I'm doing something wrong. But what???
|
| The only possibiity is that the code you just showed is not
| being executed. Absolute location 0x100 is not being overwritten
| by some timer-tick (normally) so whatever you write there should
| remain. You just put a byte of 1 in that location and then
| you compared against a byte of 1. If the CPU was broken, you
| wouldn't have even loaded your code.
Could possibly be that DS (seg register) is altered between
the store and the comparison...
| It is quite likely that the IP is being diverted around your code
| by some previous code.
|
| FYI, you can check the progress of your code by 'printing' on
| the screen. Set up ES to point to the screen segment, and write
| letters there:
|
| movw $0xb800, %ax
| movb %ax, %es
| movb $'A', %es:(0)
|
| This 'prints' an 'A' at the first location on the screen.
--
~Randy
next prev parent reply other threads:[~2003-04-23 14:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-23 13:17 Andrew Kirilenko
2003-04-23 13:33 ` Richard B. Johnson
2003-04-23 13:39 ` Andrew Kirilenko
2003-04-23 14:36 ` Richard B. Johnson
2003-04-23 14:50 ` Andrew Kirilenko
2003-04-23 15:06 ` Richard B. Johnson
2003-04-23 14:51 ` Randy.Dunlap [this message]
2003-04-23 15:11 ` Richard B. Johnson
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=20030423075158.510e25d2.rddunlap@osdl.org \
--to=rddunlap@osdl.org \
--cc=icedank@gmx.net \
--cc=linux-kernel@vger.kernel.org \
--cc=root@chaos.analogic.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
all inboxes | Powered by JetHome®