search for: get_irq_info

...wing line: === WINEDEBUG="+comm" wine .wine/drive_c/Program\ Files/SeaClear/SeaClear_2.exe What looks suspicious in the output is a continuous printing of the following two lines: --<snip>-- trace:comm:io_control 0x9c IOCTL_SERIAL_WAIT_ON_MASK (nil) 0 0x83d058 4 0x83d060 trace:comm:get_irq_info TIOCGICOUNT err Invalid argument --</snip>-- And upon exiting the app I get the followin output: --<snip>-- trace:comm:io_control 0x9c IOCTL_SERIAL_WAIT_ON_MASK (nil) 0 0x83d058 4 0x83d060 trace:comm:io_control 0x9c IOCTL_SERIAL_PURGE 0x32fe48 4 (nil) 0 0x32fddc trace:comm:io_control 0...

It is some time that I using AirMail3 with wine. I have the latest version of Wine but after I configure the Ports from ttyR0 to ttyR7 and running AirMail3 this application is not able to comunicate using the equivalent COM1 .... COM4 ports. I'm not sure if Wine is converting correctly ttyR0 to COM1 and so forth. The result is that for the Hurricane season I can NOT use E-Mail under

[cut] > > So overall the interface and extension makes sense. My only question is > > whether it's better to get complete reuse out of GET_REGION_INFO and > > GET_IRQ_INFO and then add another device tree specific ioctl or is it > > better to add a device tree index and path to the existing GET_*_INFO > > ioctls? Getting some information from one ioctl and passing pieces of > > it back to another ioctl feels a little clunky. > > > > I...

...quot;reg" and "ranges" in the device tree. >> >> 3. VFIO_DEVICE_GET_REGION_INFO >> >> No changes needed, except perhaps adding a new flag. Freescale has some >> devices with regions that must be mapped cacheable. >> >> 3. VFIO_DEVICE_GET_IRQ_INFO >> >> No changes needed. >> >> 4. VFIO_DEVICE_GET_DEVTREE_INFO >> >> The VFIO_DEVICE_GET_REGION_INFO and VFIO_DEVICE_GET_IRQ_INFO APIs >> expose device regions and interrupts, but it's not enough to know >> that there are X regions and...

...quot;reg" and "ranges" in the device tree. >> >> 3. VFIO_DEVICE_GET_REGION_INFO >> >> No changes needed, except perhaps adding a new flag. Freescale has some >> devices with regions that must be mapped cacheable. >> >> 3. VFIO_DEVICE_GET_IRQ_INFO >> >> No changes needed. >> >> 4. VFIO_DEVICE_GET_DEVTREE_INFO >> >> The VFIO_DEVICE_GET_REGION_INFO and VFIO_DEVICE_GET_IRQ_INFO APIs >> expose device regions and interrupts, but it's not enough to know >> that there are X regions and...

...ns defined > in "reg" and "ranges" in the device tree. > > 3. VFIO_DEVICE_GET_REGION_INFO > > No changes needed, except perhaps adding a new flag. Freescale has some > devices with regions that must be mapped cacheable. > > 3. VFIO_DEVICE_GET_IRQ_INFO > > No changes needed. > > 4. VFIO_DEVICE_GET_DEVTREE_INFO > > The VFIO_DEVICE_GET_REGION_INFO and VFIO_DEVICE_GET_IRQ_INFO APIs > expose device regions and interrupts, but it's not enough to know > that there are X regions and Y interrupts. User space ne...

...or the device-- corresponds to the regions defined in "reg" and "ranges" in the device tree. 3. VFIO_DEVICE_GET_REGION_INFO No changes needed, except perhaps adding a new flag. Freescale has some devices with regions that must be mapped cacheable. 3. VFIO_DEVICE_GET_IRQ_INFO No changes needed. 4. VFIO_DEVICE_GET_DEVTREE_INFO The VFIO_DEVICE_GET_REGION_INFO and VFIO_DEVICE_GET_IRQ_INFO APIs expose device regions and interrupts, but it's not enough to know that there are X regions and Y interrupts. User space needs to know what the resources are fo...

...or the device-- corresponds to the regions defined in "reg" and "ranges" in the device tree. 3. VFIO_DEVICE_GET_REGION_INFO No changes needed, except perhaps adding a new flag. Freescale has some devices with regions that must be mapped cacheable. 3. VFIO_DEVICE_GET_IRQ_INFO No changes needed. 4. VFIO_DEVICE_GET_DEVTREE_INFO The VFIO_DEVICE_GET_REGION_INFO and VFIO_DEVICE_GET_IRQ_INFO APIs expose device regions and interrupts, but it's not enough to know that there are X regions and Y interrupts. User space needs to know what the resources are fo...