linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Adrian Cox <apc@agelectronics.co.uk>
To: LinuxPPC-Dev <linuxppc-dev@lists.linuxppc.org>
Subject: copy_from_user in drivers/video/fbmem.c
Date: Fri, 16 Jun 2000 10:31:15 +0100	[thread overview]
Message-ID: <3949F3E3.996DDC77@agelectronics.co.uk> (raw)


I've just ported the chips driver in 2.2 to the 69030 (now Asiliant, was
Intel, was C&T). I've found that writing to the frame buffer device
fails, because the underlying method in fbmem.c uses copy_from_user(),
and on PowerPC copy_from_user() cannot copy into uncached space.

Which do people think is wrong:
Is copy_from_user() on PPC wrong, because it can't write to uncached
space.
Is fbmem.c wrong, because it tries to use copy_from_user() to memory
mapped IO?

- Adrian Cox, AG Electronics

ps. On the 7400 this is fairly academic, as writing sequentially to a
cache line allocates it without the need for dcbz.

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

             reply	other threads:[~2000-06-16  9:31 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-06-16  9:31 Adrian Cox [this message]
2000-06-16 11:14 ` copy_from_user in drivers/video/fbmem.c Geert Uytterhoeven
2000-06-16 14:04   ` [linux-fbdev] " James Simmons
2000-06-19 10:15   ` CTFB 0.30 now availiable (CT65554...CT69000) Thomas H?henleitner
2000-06-19 11:11     ` Adrian Cox
2000-06-19 17:31       ` Thomas H?henleitner
2000-06-19 14:12     ` [linux-fbdev] " James Simmons
2000-06-19 14:28       ` Geert Uytterhoeven
2000-06-19 14:41         ` James Simmons
2000-06-19 17:27         ` Thomas H?henleitner
2000-06-19 19:11           ` James Simmons
2000-06-20  9:03             ` name space pollution Was " Thomas H?henleitner
2000-06-20 23:40               ` 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=3949F3E3.996DDC77@agelectronics.co.uk \
    --to=apc@agelectronics.co.uk \
    --cc=linuxppc-dev@lists.linuxppc.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).