07-21-2011
No, there won't be any of the required device drivers.
8 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
will the powerbook g4, with the 16mb ati card in it be good for quake 3? (1 Reply)
Discussion started by: xeron
1 Replies
2. UNIX for Dummies Questions & Answers
I want to install Unix on my PowerBook 145b, but i have no cd-rom or diskettes, and no idea how i must install it. Can someone help me?
i would also like a x desktop, like Unixware
PowerBook 145b
M68030 16Mhz proccesor
4mb RAM
40mb HD (4 Replies)
Discussion started by: Nickdejong
4 Replies
3. AIX
Is it necessary to put system into single user mode for applying aix 5.3 TL8 on a aix 5.3.5.0 system ?
Is the TL8 installation not totally safe ?
thank you. (6 Replies)
Discussion started by: astjen
6 Replies
4. AIX
Hi,
redbook documentation is telling that IY17981 fix is required for aix 4.3.3 to aix 5L migration. But there is no mention about that fix in any ML installation packages.
- My system is ML11 :
oslevel –r
4330-11
- But xlC.rte is on wrong version :
lslpp -L xlC.rte
xlC.rte ... (3 Replies)
Discussion started by: astjen
3 Replies
5. AIX
Steps to upgrade AIX TL ( technology Level ) / Maintenance Level in AIX ( including Firmware HMC VIOS )
This article or post covers upgrades for
- Hardware Management Console ( HMC )
- Firmware ( also known as microcode )
- VIO ( Virtual I/O Server = PowerVM )
- AIX Version, Technology... (2 Replies)
Discussion started by: filosophizer
2 Replies
6. AIX
Using nimadm:
nimadm -j nimadmvg -c sap024 -s spot_6100 -l lpp_6100 -d "hdisk1" -Y
Initializing the NIM master.
Initializing NIM client sap024.
0505-205 nimadm: The level of bos.alt_disk_install.rte installed in SPOT
spot_6100 (6.1.3.4) does not match the NIM master's level (7.1.1.2).... (2 Replies)
Discussion started by: sciacca75
2 Replies
7. AIX
Hello,
I've set up email alerts on AIX Servers. so that i can get email notifications (via mail relay server) when ever there is abnormal behavior.
for example
1) my script monitors CPU/disk/memory etc... when it reaches high water ark, it will send an email alert.
2) disk usage alerts
3)... (5 Replies)
Discussion started by: System Admin 77
5 Replies
8. AIX
I am running AIX 7.1 and currently we have samba 3.6.25 installed on the server. As it stands some AIX folders are shared that can be accessed by certain Windows users.
The problem is that since Windows 10 the guest feature no longer works so users have to manually type in their Windows login/pwd... (14 Replies)
Discussion started by: linuxsnake
14 Replies
LEARN ABOUT SUSE
usb_queue_reset_device
USB_QUEUE_RESET_DEVI(9) USB Core APIs USB_QUEUE_RESET_DEVI(9)
NAME
usb_queue_reset_device - Reset a USB device from an atomic context
SYNOPSIS
void usb_queue_reset_device(struct usb_interface * iface);
ARGUMENTS
iface
USB interface belonging to the device to reset
DESCRIPTION
This function can be used to reset a USB device from an atomic context, where usb_reset_device won't work (as it blocks).
Doing a reset via this method is functionally equivalent to calling usb_reset_device, except for the fact that it is delayed to a
workqueue. This means that any drivers bound to other interfaces might be unbound, as well as users from usbfs in user space.
CORNER CASES
- Scheduling two resets at the same time from two different drivers attached to two different interfaces of the same device is possible;
depending on how the driver attached to each interface handles ->pre_reset, the second reset might happen or not.
- If a driver is unbound and it had a pending reset, the reset will be cancelled.
- This function can be called during .probe or .disconnect times. On return from .disconnect, any pending resets will be cancelled.
There is no no need to lock/unlock the reset_ws as schedule_work does its own.
NOTE
We don't do any reference count tracking because it is not needed. The lifecycle of the work_struct is tied to the usb_interface. Before
destroying the interface we cancel the work_struct, so the fact that work_struct is queued and or running means the interface (and thus,
the device) exist and are referenced.
COPYRIGHT
Kernel Hackers Manual 2.6. July 2010 USB_QUEUE_RESET_DEVI(9)