public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: root@chaos.analogic.com
Cc: Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: linux-2.4.0-test9
Date: Fri, 03 Nov 2000 20:05:15 -0500	[thread overview]
Message-ID: <3A0360CB.F534D043@mandrakesoft.com> (raw)
In-Reply-To: <Pine.LNX.3.95.1001103175055.612A-100000@chaos.analogic.com>

"Richard B. Johnson" wrote:
> I have, again, tried to use a new kernel. It is linux-2.4.0-test9
> Apparently a newer version was just put up while downloading this
> one. This is possible because it took a day to download it );

If you could download patch-2.4.0-test10, and try out test10-final, that
would be awesome...


> (3)      With the new kernel, I can't access screen memory anymore. When
> testing software drivers for hardware that I don't have, I usually use
> the screen-regen buffer to emulate the shared memory window.
> 
> Here is a snippet of code:
> 
> //    info->mem = 0xb8000     what they actually are
> //    info->mem_len = 0x4000
> 
>     if((info->vxi_iomem = ioremap(info->mem, info->mem_len)) == NULL)
>     {
>         printk(KERN_ALERT "%s: Can't allocate shared memory\n", devname);
>         (void)unregister_chrdev(info->major, info->dev);
>         kfree(info->tmp_buf);
>         kfree(info);
>         return -ENOMEM;
>     }
>     info->vxi_base   = (UNIV *) bus_to_virt(UL info->vxi_iomem);
>     ||||||||||||||
>     This pointer should point to the beginning of the screen buffer.
>     It always has before.
> 
> When accessing this from a module, I get;
> Unable to handle kernel paging requist at virtual address 800b8304.

bug 1) ioremap returns a cookie, not a bus address.  therefore, calling
ioremap output to bus_to_virt is incorrect.

bug 2) what are you doing with vxi_base?  I don't have the rest of your
code here, but I'm willing to bet that you are directly de-referencing
memory, instead of using {read,write}[bwl] / memcpy_{to,from}io.  Read
linux/Documentation/IO-mapping.txt for more info.


> (4)     More name-space polution. Somebody added another macro called
>         get_page(). When, if ever, will we start using the good-old
>         convention of defining macros in upper-case?
> 
>         The name-space polution has really gotten out-of-hand. You
>         can't write code using ordinary symbol names anymore. You
>         need to make variables have names like:
> 
>         int LoopCounterForOutSideLoop;
>         char *UserInputAndOutputBufferForWednesday;
> 
>         This is NotGood(tm)

I guess it should probably have been named "page_get"?  I looked through
'nm vmlinux' output at the public symbols, and there are definitely a
ton of them.

Though it is definitely C convention that macros are in all uppercase
(gcc is good about this), the kernel has never really been good about
that...

	Jeff


-- 
Jeff Garzik             | Dinner is ready when
Building 1024           | the smoke alarm goes off.
MandrakeSoft            |	-/usr/games/fortune
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2000-11-04  1:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-03 22:54 linux-2.4.0-test9 Richard B. Johnson
2000-11-04  1:05 ` Jeff Garzik [this message]
2000-11-04  2:49   ` linux-2.4.0-test9 Richard B. Johnson
2000-11-04  3:12     ` linux-2.4.0-test9 Jeff Garzik
2000-11-04  8:20       ` linux-2.4.0-test9 Ingo Oeser
2000-11-04  8:26         ` linux-2.4.0-test9 Jeff Garzik
2000-11-04 10:55 ` linux-2.4.0-test9 Keith Owens
2000-11-06 14:45   ` linux-2.4.0-test9 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=3A0360CB.F534D043@mandrakesoft.com \
    --to=jgarzik@mandrakesoft.com \
    --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