From: Juan Perez-Sanchez <lithoxs@gmail.com>
To: linux-8086 <linux-8086@vger.kernel.org>
Subject: [PATCH 3 of 5] General improvements to arch dependent code
Date: Tue, 29 May 2012 15:09:47 -0500 [thread overview]
Message-ID: <CAD6VGuYvf57aKk9CY8r3jsVz7xT5Wp=_djdojFmgtat7ofqHyw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 765 bytes --]
Hi,
This patch implements:
1. Updated file "arch/i86/sibo/irqtab.c" to work the same way as
"arch/i86/kernel/irqtab.c". That is, simpler, faster, smaller and
easier to understand code.
2. Removed the following unused variables from irqtab.c:
off_stashed_irq0
seg_stashed_irq0
stashed_ss
stashed_sp
stashed_irq
bios_call_cnt
stashed_di
cs_tmp
IRQdata_offs
There is a reduction of 16 bytes in code size.
Kernel was built with options Architecture SIBO, SSD disk support
enabled and network support disabled. The kernel built without errors,
but I have no means to test this architecture.
The kernel was built and the Image tested in qemu and dioscuri
emulators. Also tested in a PPro booting from floppy.
Greetings,
Juan
[-- Attachment #2: elksD.patch --]
[-- Type: application/octet-stream, Size: 10147 bytes --]
reply other threads:[~2012-05-29 20:09 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CAD6VGuYvf57aKk9CY8r3jsVz7xT5Wp=_djdojFmgtat7ofqHyw@mail.gmail.com' \
--to=lithoxs@gmail.com \
--cc=linux-8086@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 read-only IMAP folder(s) and NNTP newsgroup(s).