1 May 2002 16:47
Request for suggestion on a user space map-er for memory IO space
Boris Itkis <borisitk <at> fortunet.com>
2002-05-01 14:47:11 GMT
2002-05-01 14:47:11 GMT
I am working on a clean way of mapping IO memory space for the ARM (Other processor also but I am testing this on the arm). On the x86 platform there is ioperm which allows supper-user apps to access IO space. This is not available on the ARM since there is only one address space (On the ARM all IO is in memory space). An equivalent system is needed for the ARM. I have heard there are patches that modify the mmap code in the kernel so user space apps can map IO memory space into the apps memory space. This approach is not clean and unnecessarily complicates the sys_mmap code. My solution is to have a file which is the IO memory space (I chose a file instead of a device since Linux 2.4 is running low on major numbers). The file is part of the proc file system. I have a proc entry that allows one to list and optionally add new IO areas ( I will later add a way to optionally delete areas/files). By having memory area (a file) that is part of the file system a user app can mmap it as any other file in the file system. And by having module add itself to the proc file-system all the changes are confined to one file. My question's: 1. I am putting all my files into root of the proc file system. Any better suggestions? 2. What is the best name for the area/file list-er? I am currently using "UserIoRegions". 3. Where should I but this code into the Linux directory tree? (It can be a module or part of the kernel) 4. A related question is where to put it into the Linux config tree? (Where(Continue reading)
RSS Feed