Greg KH wrote:

>On Mon, Mar 07, 2005 at 05:48:56PM -0500, Wen Xiong wrote:
>  
>
>>Since some tools in Digi company need these new ioctls to access device 
>>driver. I still keep these new ioctls.
>>    
>>
>
>What tools?  What are they used for?  Why do they need them?  Why can't
>they just use the sysfs files?  
>
>As the driver isn't in the kernel tree, there should not be any users
>expecting these ioctls to be around, right?
>
>thanks,
>
>greg k-h
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at  http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at  http://www.tux.org/lkml/
>
>  
>
Hi Greg,
I exchanged emails with digi developer,  I scrubbed out some structs and 
ioctls aren't being used by this driver.
Only keep some structures for management ports. After scrubbed the 
digi.h, I combined two headers to one header.
Hope you like  it this time.

Thanks,
wendy

The following email I got from Scott Kilau in digi:
Scott Kilau wrote:

        The DPA program is very old, and is shared among other drivers 
and OS's,
        so changing the code to read the sysfs instead of doing ioctls 
is not possible.
        However, any *new* tools I write, will use sysfs, which is why 
we need to have both the ioctl calls and sysfs files.
        The digi.h file has extra structures and ioctls that may not be 
used in the driver, as that header
        is shared among other drivers and OS's.