Prolem met when porting device driver to Solaris 2.4

Prolem met when porting device driver to Solaris 2.4

Post by aaron tse » Wed, 06 Sep 1995 04:00:00



    Dear All:

          Urgent !!!! please help me !

          I am running a project and trying to port a device driver to
        Solaris 2.4 on x86 machine. I need to know how to convert kernel
        address allocated from kmem_alloc() to physical address and the
        address space must be contiguous. In SCO UNIX there are ktop() and
        ptok() to solve this problem, in AT&T UNIX there are phystokv() and
        vtop() to solve this problem, could anybody tell me in Solaris 2.4
        how to solve this problem ? By the way, can I use ddi_iopb_alloc()
        and hat_getkpfnum() to solve this problem ?

    Best Regards,
    Aaron Tseng on 09/05/95        

--
========================================================================        

Adapter Product Center              Tel : 886-35-779966 Ext 3326
D-Link Corp., HsinChu, Taiwan       Fax : 886-35-777154                        

 
 
 

1. Porting device driver from 2.2 to 2.4

Hi,

I have successfully compiled (without code changes) and installed my device
driver (which was originally build for kernel 2.2) under kernel 2.4.4, but it
doesn't work anymore. The major/minor number supplied to the filesystem
operations is always zero. For example in  

mydev_open(struct inode *inode, struct file *filp)

inode->i_rdev is zero. The major/minor of the device node is not zero
and corresponds to the number shown in /proc/devices. Are there any
incompatibilities between kernel 2.2.x and 2.4.x? Do I have to change my
code in some aspects? Note: I do not use devfs and the kernel is not compiled
with devfs.

Thanks

Helmut

2. routing admin question for sol7

3. Solaris 2.4: system calls in device driver

4. Linux Red Hat install

5. ctrl in the device driver of solaris 2.4

6. FW Update failed

7. Device driver for Solaris x86 2.4

8. fvwm95-2 help

9. Sun Sparc Solaris 2.4 Device Driver For Zilog 8530

10. Added interrupt routine for a device driver under Solaris 2.4

11. solaris 2.4 memory mapped SBUS device drivers

12. Serial device driver hangs Solaris 2.4 x86