** Reply to message from Alan Cox <[EMAIL PROTECTED]> on Mon, 2 Oct 2000
17:18:59 +0100 (BST)
> > Anyway, my original question has not yet been answered: why is it that I can
> > ioremap() any physical page by simply setting one bit, but I cannot always
> > iounmap() it? Why can't iounmap() sim
> Anyway, my original question has not yet been answered: why is it that I can
> ioremap() any physical page by simply setting one bit, but I cannot always
> iounmap() it? Why can't iounmap() simply undo what ioremap() did?
The fact you can doesn't mean you should. You need to be sole owner of t
** Reply to message from Alan Cox <[EMAIL PROTECTED]> on Sat, 30 Sep
2000 00:24:43 +0100 (BST)
> > Unfortunately, this mapping is a requirement for our product. I'd hate to have
> > to create my own pte's and do it all manually.
>
> If you are doing it at boot time as Id expect then you may ne
> Unfortunately, this mapping is a requirement for our product. I'd hate to have
> to create my own pte's and do it all manually.
If you are doing it at boot time as Id expect then you may need to - the SMP
code for bootstrapping has to do pte stuff itself for the same reason
-
To unsubscribe f
** Reply to message from Alan Cox <[EMAIL PROTECTED]> on Fri, 29 Sep
2000 23:00:16 +0100 (BST)
> > "num_pages" is usually just equal to 1. This code appears to work very well.
> > However, when I call the iounmap function on the memory obtained via
> > ioremap_nocache, sometimes I hit a kernel
> "num_pages" is usually just equal to 1. This code appears to work very well.
> However, when I call the iounmap function on the memory obtained via
> ioremap_nocache, sometimes I hit a kernel BUG(). The code which causes the bug
> is in page_alloc.c, line 85 (in function __free_pages_ok):
>
6 matches
Mail list logo
