From: Nathaniel <wfilardo@fuse.net>
To: Linus Torvalds <torvalds@transmeta.com>,
linux-kernel@vger.kernel.org, Alan Cox <alan@redhat.com>
Subject: Re: Linux 2.5.30
Date: Sat, 03 Aug 2002 01:16:45 -0400 [thread overview]
Message-ID: <3D4B673D.4050507@fuse.net> (raw)
In-Reply-To: Pine.LNX.4.33.0208021424520.2532-100000@penguin.transmeta.com
Linus Torvalds wrote:
> On 2 Aug 2002, Alan Cox wrote:
>
>>The PnPBIOS gdt setup changes I did are wrong somewhere.
>
>
> Alan, in your PnP patches you seem to have changed the
>
> "set_limit()"
>
> to a
>
> "_set_limit()"
>
> which looks wrong (or at least doesn't look consistent with the notion of
> just doing the same code as before, except on all CPU's).
>
> It _looks_ to me like the QX_SET_SET() macros should be have the "_"
> removed from the set_limit part. As it is, _set_limit() gets the address
> calculations wrong (because you don't cast it to "char *") and also gets
> the limit wrong (because you no longer do the page size adjustment).
>
> Does it work with that small change? I have no idea about the pnpbios
> code, I'm just looking at Alan's diff.
Applying the following change will make 2.5.30 get past the PNPBIOS load (at least on my box).
However, it still doesn't work (I'll post something later).
That said, here:
--- linux-2.5.30/drivers/pnp/pnpbios_core.c.orig Sat Aug 3 01:13:48 2002
+++ linux-2.5.30/drivers/pnp/pnpbios_core.c Sat Aug 3 01:13:20 2002
@@ -126,11 +126,11 @@
#define Q_SET_SEL(cpu, selname, address, size) \
set_base(cpu_gdt_table[cpu][(selname) >> 3], __va((u32)(address))); \
-_set_limit(&cpu_gdt_table[cpu][(selname) >> 3], size)
+set_limit(cpu_gdt_table[cpu][(selname) >> 3], size)
#define Q2_SET_SEL(cpu, selname, address, size) \
set_base(cpu_gdt_table[cpu][(selname) >> 3], (u32)(address)); \
-_set_limit((char *)&cpu_gdt_table[cpu][(selname) >> 3], size)
+set_limit(cpu_gdt_table[cpu][(selname) >> 3], size)
/*
* At some point we want to use this stack frame pointer to unwind
--Nathan
next prev parent reply other threads:[~2002-08-03 5:13 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-01 21:30 Linux 2.5.30 Linus Torvalds
2002-08-01 23:32 ` Banai Zoltan
2002-08-02 0:12 ` Alexander Viro
2002-08-02 0:38 ` Banai Zoltan
2002-08-02 3:17 ` Linus Torvalds
2002-08-02 12:23 ` Alan Cox
2002-08-02 16:57 ` Thomas Molina
2002-08-02 21:29 ` Linus Torvalds
2002-08-03 5:16 ` Nathaniel [this message]
2002-08-02 1:25 ` Linux 2.5.30: [SERIAL] build fails at 8250.c Axel Siebenwirth
2002-08-02 17:13 ` Russell King
2002-08-02 19:19 ` Axel Siebenwirth
-- strict thread matches above, loose matches on Subject: below --
2002-08-02 1:36 Linux 2.5.30 Douglas Gilbert
2002-08-02 6:37 ` James Simmons
2002-08-01 3:30 Ivan Gyurdiev
2002-08-02 6:03 ` James Simmons
2002-08-02 11:29 ` Helge Hafting
2002-08-02 14:32 ` James Simmons
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=3D4B673D.4050507@fuse.net \
--to=wfilardo@fuse.net \
--cc=alan@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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