[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [MiNT] GlueSTiK and mem protection

To: MiNT mailing list <mint@atari.archive.umich.edu>
Subject: Re: [MiNT] GlueSTiK and mem protection
From: Scott Bigham <dsb@cs.duke.edu>
Date: Thu, 3 Jun 1999 19:28:31 -0400 (EDT)
In-reply-to: <Pine.HPP.3.91.990603134937.18022B-100000@csmd44>
Sender: owner-mint@fishpool.com

On Thu, 3 Jun 1999, Frank Naumann wrote:

> > allocated with kmalloc() ? [...]

> You are right. Gluestik must allocate such memory in user area.

You're sure of this?  This is happening inside the device driver; I
didn't think umalloc() could be used there.  Is there a way to simply
change the visibility of the memory so that it can be seen by user
programs, or does the user program need to be able to change the
contents of the CIB?

						-sbigham

Follow-Ups:
- Re: [MiNT] GlueSTiK and mem protection
  - From: Frank Naumann <fnaumann@prinz-atm.CS.Uni-Magdeburg.De>

References:
- Re: [MiNT] GlueSTiK and mem protection
  - From: Frank Naumann <fnaumann@prinz-atm.CS.Uni-Magdeburg.De>

Prev by Date: Re: [MiNT] New set_mmu and tools
Next by Date: Re: [MiNT] MiNT and PureC
Previous by thread: Re: [MiNT] GlueSTiK and mem protection
Next by thread: Re: [MiNT] GlueSTiK and mem protection
Index(es):
- Date
- Thread