Sunday Mar 13, 2011

New hotplug(1M) command in Solaris

Solaris users are familiar with cfgadm(1M) for hotplug devices since
many years ago. This system admin tool is based on plugins. That is,
for each data bus, like PCI, usb, SCSI, etc., there is a cfgadm plugin
for interpreting the sub-commands. And it supports physical hotplug
only.


Now there is a new system admin tool hotplug(1M) for user's
choice. Currently it supports PCI/PCIe hotplug only, because the
underlying hotplug controller drivers for other data buses are not
ported to the new Solaris Hotplug Framework yet. But it is expected
that, in the future, more and more bus drivers would be ported to it.



One benefit from the new tool is, it supports "virtual hotplug". That is,
arbitrary devices could be hot add/removed from the device tree,
logically. This feature could contribute to the applications in virtualization environment.


Before running hotplug(1M) command at the first time, user need to
enable hotplug service by running 'svcadm enable hotplug'. This service is not
enabled by default.

Wednesday Dec 03, 2008

Migrate to zfs root via live upgrade on Solaris

My desktop was installed solaris before zfs integrated. I upgraded it to build 93 via live upgrade first. Then, I want it run on zfs root. The following is the detail steps I migrate it to zfs. Not difficult, not very straightforward.


# lustatus
Boot Environment           Is       Active Active    Can    Copy     Name                       Complete Now    On Reboot Delete Status   -------------------------- -------- ------ --------- ------ ----------
1                          yes      yes    yes       no     -      


2                          yes      no     no        yes    -      


# lufslist 2
              boot environment name: 2

Filesystem              fstype    device size Mounted on          Mount Options
----------------------- -------- ------------ ------------------- --------------
/dev/dsk/c1t0d0s1       swap       2640314880 -                   -
/dev/dsk/c1t0d0s3       ufs       19732446720 /                   -
/dev/dsk/c1t0d0s7       ufs      157086397440 /export/home        -


# lufslist 1
              boot environment name: 1
              This boot environment is currently active.
              This boot environment will be active on next system boot.

Filesystem              fstype    device size Mounted on          Mount Options
----------------------- -------- ------------ ------------------- --------------
/dev/dsk/c1t0d0s1       swap       2640314880 -                   -
/dev/dsk/c1t0d0s0       ufs       19740672000 /                   -
/dev/dsk/c1t0d0s7       ufs      157086397440 /export/home        -

# ludelete 2
System has findroot enabled GRUB
Checking if last BE on any disk...
BE <2> is not the last BE on any disk.
Updating GRUB menu default setting
Changing GRUB menu default setting to <0>
File </boot/grub/menu.lst> propagation successful
File </etc/lu/GRUB_backup_menu> propagation successful
Successfully deleted entry from GRUB menu
Determining the devices to be marked free.
Updating boot environment configuration database.
Updating boot environment description database on all BEs.
Updating all boot environment configuration databases.
Boot environment <2> deleted.

# zpool create mpool c1t0d0s3
invalid vdev specification
use '-f' to override the following errors:
/dev/dsk/c1t0d0s3 overlaps with /dev/dsk/c1t0d0s2
# zpool create -f mpool c1t0d0s3

# lucreate -c 1 -n 2  -p mpool
Checking GRUB menu...
System has findroot enabled GRUB
Analyzing system configuration.
Comparing source boot environment <1> file systems with the file system(s)
you specified for the new boot environment. Determining which file systems
should be in the new boot environment.
Updating boot environment description database on all BEs.
Updating system configuration files.
The device </dev/dsk/c1t0d0s3> is not a root device for any boot environment; cannot get BE ID.
Creating configuration for boot environment <2>.
Source boot environment is <1>.
Creating boot environment <2>.
Creating file systems on boot environment <2>.
Creating <zfs> file system for </> in zone <global> on <mpool/ROOT/2>.
Populating file systems on boot environment <2>.
Checking selection integrity.
Integrity check OK.
Populating contents of mount point </>.
Copying.

# luupgrade -u -n 2 -s /net/bounty/export/nv/solarisdvd.nvx_dvd/101a

# luactivate 2
# init 6


After reboot, it goes to boot environment 2 and run on a zfs root.

Monday Oct 20, 2008

Use ekiga and a usb webcam for video conference

It is easy to setup a video conference by using ekiga.


1. Plug your USB webcam.
(See the list of webcams supported on opensolairs)

You then should have the device file /dev/video0 created automatically.


2. Configure ekiga with GUI.


When the first time running Ekiga or you click Ekiga menu
Edit -> Configuration Druid, you can see a dialog pop up. After click
"Forward" button for a couple of times, you see a dialog to ask for an
account, you can just click "I do not want to sign up for the ekiga.net
free service", and then go forward. When you are asked for choosing
"Video Manager", please choose V4L2. After these configuration steps,
you
can see the application window, and then click the video camera button
to see
the video. Now you will see the local video captured by your usb webcam.


3. To connect with others to see the remote video.


It is easy to use h323 protocol to connect two PCs. Just one step:


In the address blank of Ekiga main window, type:
h323:hostname,
or
h323:ip-address, e.g., h323:192.111.111.1

The hostname or ip address belong to the PC that you want to call. Then type return or click the call button to issue the call. After the peer accepted the call, then you are connected. Remote video will be displayed on both sides.


Note:
If ekiga can not detect the webcam but the /dev/video0 file is already created, it might be the file permission problem. The access to /dev/video0 is
granted to login user only. So, if you are running ekiga using another user
name, then ekiga can not detect the webcam. Just change the user to the
login user will make it work.


Tips:
After you are connected, clicked the "View" menu to try various ways of displaying remote/local video or zoom the video.

Sunday Jun 22, 2008

ugen driver in Solaris


ugen (USB generic) driver in Solaris is useful for users because it exports device nodes for each of the end point of a USB device. Users can access the raw data of the USB device via the ugen nodes. libusb or openusb interfaces are built upon this driver. It is not that staight forward that in what cases ugen nodes will be exported. Recently I was asked by people who want to utilize ugen device nodes in their projects. The following is trying to summarize all the cases.

ugen nodes are exported by default for the following devices:
1. Any USB devices that have not a class or vendor unique driver in
solaris.
2. USB storage devices bound to scsa2usb(7D) driver. (refer to
scsa2usb(7D) manpage)
3. USB printer devices bound to usbprn(7D) driver. (refer to
usbprn(7D) manpage)
4. For a multi-interface USB device, usb_mid driver is by default
attached to it.

If none of the device's interfaces are explicitly
bound to the ugen(7D) driver, then usb_mid driver will create ugen
nodes for the device.

ugen nodes are not by default exported for some USB devices (a USB mouse, for example),
because it is bound to hid driver by USB class number and hid driver
does not create ugen nodes.

Thursday Jun 12, 2008

A simple VNC step-by-step experience on OpenSolaris

VNC is really a good tool for sharing desktops to your remote peers.
The following is my personal experience with VNC on OpenSolaris. I am
running OpenSolaris build 86. It should be the same case in other
builds.


1.
Check the binaries I am using:

$ which vncserver

/usr/bin/vncserver

$ which vncviewer

/usr/bin/vncviewer


2.
I add a new user "vncuser" with "Basic Solaris User" privilege.
(This step is just my personal favor. But it helps you to have a clean
test environment.)

# users-admin


3.
Try the first run.

$ su - vncuser

$ vncserver


Some files will be created in $HOME/.vnc/ directory, including "xstartup".

Connect to the vncserver.

$ vncviewer localhost:1


A VNC desktop window appears.


4.
The default window manager seems not that good. Edit the file
"xstartup" to use JDS desktop. Comment all lines, and add
"gnome-session" to it.

$ cat xstartup

#!/bin/sh


#[ -r $HOME/.Xresources ] && xrdb $HOME/.Xresources

#xsetroot -solid grey

#vncconfig -iconic &

#xterm -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" &

#twm &

gnome-session


5.
Run vncserver again. This time I specify more options to customize
it a bit. (Check manpage vncserver(1) for details of the options.)

$ vncserver :16 -alwaysshared -deferupdate 100 -geometry 1024x768 -depth 16


Run vncviewer:

$ vncviewer localhost:16


I then see a nice desktop window appears.


BTW, to kill the VNC servers that are run above, just type:

$ vncserver -kill :1

$ vncserver -kill :16

Monday Jun 02, 2008

Association: The Difference between USB and Wireless USB

The Wireless USB technology from usb.org tries to make it easy for end
users to connect a wireless USB device with a wireless USB host, quoted
from the specification: “The goal is that end users view it as the same
as wired USB, just without the wires.
”. However, there have to be
something different because of the difference of wireless and wired
environment. The most significant thing is "Association". It is
something happened before the first time that a wireless USB device can
be enumerated by the host system.

Association is special for wireless host and device, it is new for
wired USB users and it is not a straight forward concept for most
people. But if we take a look at the following question, we might know
it well.

Suppose two PC boxes are put in one room, each of them has a WUSB host.
A user brings a WUSB device to the room and turn on the device radio.
The question is, which PC box should enumerate the device? Or the
question can be asked in another way, how can the user choose a PC box
with which he would like to connect the wireless device?

It is not a question at all if in a wired case: the user just plug the
device to the PC box with which he want to connect the device. In
wireless case, a new way must be invented to let the specific wireless
hosts and devices know that which device should be connected to which
host. So, usb.org comes the technologies called "Association Model". It
makes the specific WUSB host and device create a shared CC (Connection
Context). A CC includes three elements: CHID (Connection Host ID), CDID
(Connection Device ID), CK(Connection Key). Once the CC is created
during the association process, it will be saved in the non-volatile
memory on both host and device. Thus, the host and device will "know"
each other and trust each other in a wireless environment.

According to WUSB specification, there are two Association Models optional for device manufactures and users.

- Cable Association

  User need to connect the WUSB device with his PC box with a USB cable
for a few seconds. The WUSB host on the PC box then talks to the device
to create a CC. The user then unplug the WUSB device and need not to
plug it any longer, unless he decide to connect the WUSB device with
another PC. With the CC stored in both WUSB host and device, when user
turn on the device radio, because the device and host already know each
other, they can authentication each other and be connected just as
wired USB. The only difference is, the connection is over air.

- Numeric Association

  User need not a USB cable in this case. But the WUSB device need to
have a screen to display digit numbers. The process is, user turns on
the device radio, and run the WUSB administration software on the host
to specify a WUSB host on the system to start to associate itself with
the device which is beaconing. The specified WUSB host then talk to the
device over air and create a CC. Because it is performed in the open
radio, user is asked manually confirm the association. A digital number
is displayed both on the host system screen and the device screen. If
they are the same, user press OK on both sides. If not, then the
association is not right.

From the host software's view, there must be an utility to manage the
CCs stored in host system. Because, on one system (e.g., a PC box),
there could be multiple WUSB hosts. And also, there could be multiple
WUSB devices associated with a WUSB host. What's more, when system
booting up, a daemon is needed to load the CCs from file system to the
WUSB host driver instances. A specific CC belongs to a specific WUSB
host instance.
To support the above issue, on Solaris, a software design is under
review. A daemon wusbd is introduced to be used to manage the CCs for
WUSB hosts and devices. It add/remove the CCs to CC database, load the
CC to host driver instances. A admin tool wusbadm is introduced for
user interfaces. It sends requests to wusbd when needs to operate CCs.

After the association process, from the host software view or the end
user view, it is all the same as wired USB devices, e.g., device
enumeration, USB client driver attach, connect/disconnect event
handling, devfs nodes, etc.

One of the goals for this design is the similar as the what the WUSB
spec tells, to have a simple user interface and make end user view WUSB
the same as wired ones. Connect and play, just without wires. Users
just need to turn on the device radio to connect, or, turn off the
device to disconnect. And something better in WUSB case: there are
always enough "ports" there. A WUSB host is supposed able to connect up
to 127 WUSB devices, theoretically. So, you just put WUSB devices
around your PC box, associated for once, then enjoy them as USB ones,
and without wires.

Friday Feb 15, 2008

Snow, Snow and Snow!

There is a Chinese saying, “瑞雪兆丰年”, which means “a snow year, a rich year”. However, in this winter, if we ask a question to a person who lives in China, “What impress you most in this winter?”, I believe most likely the answer is “too much snow”. No doubt, there is a very bad snow disaster in south China in recent months. Because of the heavy snow, a lot of people could not go to hometown for Chinese new year holidays; a lot of towns could not have stable power supply; a lot of people had to stay in cars or trucks for days because the highways were blocked; and, the worst, some people living in villages were facing the risk of starving because they ran out of food and could not be reached by outside world. In the TV news, I saw that soldiers had to drive armored vehicles to carry food to a village. Disaster, a word that seems not that closely related with our daily life, now seems so near with us.

Although I myself am not living in south China and do not experience the heavy snow, I am feeling the disaster though TV programs, newspapers and Internet. Because most of the recent news are about it. I lived in south China in my childhood, so I understand how much troubles the snow disaster would bring to the people living there.

Disasters are horrible, but they can not damage that much if we are prepared against it. Every time I see people struggling in the snow in the TV news, I was always thinking about a question, are there anything we could do to prepare against the disasters, especially in our daily life or work?

Every time after a disaster strike, people will always say: “if we got bla bla prepared, then the damage will be much less than what we got”. While government should do a lot to prepare against disasters, individuals can also do something in our daily life or work. I believe it will help a lot if the huge population would think about it and contribute a bit. I myself thought about it and have some straightforward ideas:

1. Subscribe to weather forecast and be serious to bad weather warnings. If people would cancel their travel plans in the areas covered by snow disaster, then fewer people will be blocked in the railway stations and no one would be treaded to die.

2. Save power in daily life and work. In the snow disaster, we see that a big problem is the lack of coal for power plants. If all of us have good habits to save energy, then, less coal and power are needed, fewer problems we will have. On the other hand, when disasters come, we will have more energy to deal with them.

3. If you are an engineer, you are so lucky that you could contribute more. For example, you can try to develop better technologies for people to do telecommunication. People can then meet their family members over distance as if they were in one room, instead of have to travel in bad weathers.

OK, I have talked a lot about snow. For the other sorts of disasters, they are the similar cases. For example, investigation reports tell that some forest fires were caused by small cigarettes. If all of us would stop smoking, then the risk of having a forest fire would be decreased a lot. Let’s keep the world and ourself clean.

I love snow, because it is white, clean and beautiful. What’s more, I can enjoy skiing in the winter. I hate snow, because it causes traffic problems and too much of it will make a disaster. Fortunately, we can learn to get prepared against it. As long as we are prepared for it, we will just enjoy it.

Saturday Dec 15, 2007

In practice: Ekiga video conference

It happened on this Tuesday (December 11, 2007). By running the latest Solaris Express on laptops, we had the first dual way Ekiga video conference between Sun engineering teams in Beijing and headquarter staff in MPK, US. During the whole meeting, which lasted more than one hour, the video stream is quite stable and the video quality is fine. I like video conferences much than audio only ones. People smile to each other and wave to each other, very nice. Many people know each other by emails or by conference calls, now, they see faces and smiles.

Not like some dedicated video conference equipments, the hardware equipments we used are very simple, just a laptop + a webcams + a projector. All are low cost commodity devices. In Beijing conference room, we use a Lenovo laptop running Solaris Express (build 76) and a Logitech USB webcam. US staff were using the similar equipments.

More detail usage info about Ekiga application and USB webcam driver can be found in my previous blogs:
USB webcams and video conferencing on Solaris
Have a larger video size in Ekiga

Monday Nov 26, 2007

amsn on OpenSolaris

amsn is a nice instance chatting application. It supports video chatting. A talent community member just ported it to Solaris. I received emails from him and had a chance to see the screen shots of amsn running on Solaris. It looks great! The video is captured from a USB webcam which is supported by usbvc(7D) driver. The following link is also from him, the patch for Solaris is submitted to amsn community:

http://www.amsn-project.net/forums/viewtopic.php?p=25214#25214

I believe Solaris users will enjoy it!
 

Have a larger video size in Ekiga

Learned from an Ekiga developer, Ekiga supports a larger video size if you change the default value by gconf-editor. It is easy to have a larger video size in Ekiga application. I tried the following on my Solaris desktops, it works.

Login JDS, run 

# gconf-editor

In the gconf-editor window, select apps->ekiga->devices->video->size. Change the value of size from 0 to 1. Before quit, click somewhere else to save the change. Done.

Note, you need to "fully" quit Ekiga before change the above value. My favorite way is to run 'pkill ekiga' first.

Thursday Oct 04, 2007

Build OpenSolaris Step by Step


The following are steps to build OpenSolaris. My co-workers and I figured out these steps according to the documents on OpenSolaris.org. These steps are easy to follow and tested on Solaris Express build 63.

1. Download & Install Build Environment:

1.1 Download Compiler (Sun Studio is the preferred compiler, and it is free)
Install the compiler according to the instructions at the download site.
The result should have the compilers installed in /opt/SUNWspro.

1.2 Download ON build tools package (SUNWonbld.PLATFORM.tar.bz2)
http://dlc.sun.com/osol/on/downloads/current/
and install:

# cd $TEMP
# bunzip2 -c SUNWonbld.i386.tar.bz2 |tar xvf -

# yes y | pkgadd -d ./ SUNWonbld

1.3 Fetch ON (OS & Network) source code

# hg clone ssh://anon@hg.opensolaris.org/hg/onnv/onnv-gate

Source tar balls have been deprecated in favour of the onnv project's Mercurial repository. Please see the onnv project page for more information on how to checkout/clone the repository to download the source.

1.4 Download Encumbered binaries tarball (on-closed-bins[-nd].PLATFORM.tar.bz2) for debug and non-debug version

http://dlc.sun.com/osol/on/downloads/current/

Need to extract from tarball and put root_i386 and root_i386-nd under $CODEMGR_WS/closed,

For example:

If the source code is in "/export/testws/usr/src", then the binaries will be in "/export/testws/closed/root_PLATFORM"
(i.e., closed/root_i386 or closed/root_sparc). For non-debug version, it is closed/root_i386-nd or closed/root_sparc-nd.

2. Environment setup


2.1 PATH

# PATH=/opt/SUNWspro/bin:/opt/onbld/bin:/opt/onbld/bin/i386:$PATH

2.2 Copy and set environment file

# cp usr/src/tools/env/opensolaris.sh /export/testws/
modify opensolaris.sh for your $CODEMGR_WS, $STAFF, $MAILTO settings

  • change GATE to none or the name of the top-level directory (e.g., "testws").

  • change CODEMGR_WS to the your workspace (e.g., "/export/testws").

  • change STAFFER to your login (e.g., root).

  • (optional) change MAILTO to you email address.

  • (optional) customize VERSION. This is the string that "uname -v"
    will print.

3. Build

3.1 Nightly Build (build the whole ON source)

# nightly ./opensolaris.sh & tail -f log/nightly.log
nightly options:

  • -n: no bringover (default)

  • -i: incremental build (no clobber)

  • -D: do a build with DEBUG on

  • -F: do not do a non-DEBUG build

3.2 Single module Build

  • make a single module:
    bldenv opensolaris.sh; cd usr/src/uts/intel/i915; make
[ Reference links]

  • ON source
  • SUNWonbld
  • on-closed-bins

Thursday Sep 27, 2007

New USB webcams tested on Solaris

I received five Logitech webcams weeks ago. They are all new models, very fancy. I then had a quick test on Solaris Express. Four of them work well with Ekiga application integrated in Solaris, just plug and play. One of them can not work, the reason is that it does not conform to USB video class spec from usb.org, it needs chip specific driver. The other four webcams passed more tests later. I have updated one of my previous blog to add the names of them to a device list which tells all the tested webcams on Solaris video class driver (usbvc(7D)).

 Device Name                          Vendor ID, Product ID

Logitech Quickcam Pro for Notebooks       046d,0991
Logitech Quickcam Deluxe for notebooks    046d,09c1
Logitech Quickcam Communicate Deluxe      046d,0992
Logitech Quickcam Pro 9000                046d,0990

So far, there are about 9 or more webcams are supported by Solaris video class driver (usbvc(7D)). Again, for a full device list, please refer to my updated blog for USB video webcams and applications.

Tuesday Jul 17, 2007

Data Alignment Issue


If a data structure will be used in both a 32bits binary and a 64bits
binary, e.g., an ioctl structure which is passed from a 32bit
application to the 64bit kernel, then we need to consider the code
alignment issue. Because:

  •   The structure size might be different for a same structure.
  •   The offset of each structure member might be different for a same
    structure.

The alignment can be decided by compiler options. The default compiler behavior will conform to the top rule: all structure members must start at its alignment addresses, and, the whole structure should start at the alignment address of its largest member.
For example, uint16_t will always start at even address, uint32_t will always align at 4 bytes boundary, etc. There are also some points as following:

  1.  

    The whole structure's size will be according to the biggest member's
    alignment. e.g., if the biggest member is uint32_t, then the whole
    sizeof(struct) will be divided exactly by 4bytes.

  2.  

    If there are "long", "pointer", or "long double" types in the
    structure
    members, then the alignment in 32bit and 64bit binaries will be
    different. Because they are different length. For example, if there is
    a pointer in a structure, then, in a 32bits binary, it aligns at 4
    bytes
    address; in a 64bits binary, it aligns at 8 bytes address.

  3.  

    The max alignment of 32bits binary is 32bits, The max alignment of
    64bits binary is 64bits. So, if there is a "long long" in a 32bits
    binary, it aligns at 4 bytes address; however, the same type aligns at
    8 bytes address in a 64bits binary.

  4.  

    "enum" type is considered as uint_t.

Code alignment feature can be disabled by setting specific compiler options, such as, gcc -fpack-struct, which will remove the code alignment feature, that is, there are no gaps between structure members.

And "pack" pragma can also do the same job, details refer to the related section of "C User's Guide". Note that the pragma might cause problems on different hardware platforms.

The following table is comparing the data types between 32bits and 64bits binaries.

C Type                      ILP32                LP64
 

char                            8                    8
  short                          16                   16
  int                              32                   32
  long                           32                   64
  long long                   64                   64
  float                           32                   32
  double                       64                   64
  long double               96                   128
  pointer                      32                   64


-----------------------------
An data structure Example:


    typedef enum list {

        a0 = 0,

        a1 = 1,

        a2 = 2,

    } list_t;


    struct align {

        uint16_t a;

        uint8_t  b;

        list_t    list;

        uint8_t    c;  

        uint8_t    d;  

    } sa;


offset_a=fffffd7fffdff954, offset_b=fffffd7fffdff956,
offset_list=fffffd7fffdff958, offset_c=fffffd7fffdff95c,
offset_d=fffffd7fffdff95d, sizeof_allign=12

Saturday Jun 30, 2007

"Real-Time" and Desktop User Experience


There are billions of desktop users in the world, it means a lot to
improve computer system for them. As a desktop user and a software
engineer, I've thought a lot regarding as desktop user experience
recently.  I think there are a lot of relationship between "Real-Time"
and Desktop User Experience.

My Ph.D. thesis is about real-time operating system. From academic
view, in computer science, the term "Real-Time" has an strict
definition, it mainly means, in a real-time system, a compute task must
be completed within the expected time. In practice, especially in the
desktop area, while its academic meaning is sometimes still kept, this
term also means "quick response to user's instructions". Desktop users
always would like their computers behave in a real-time way, for
example, they would like the audio/video player always output smoothly
instead of having pauses; they would like the application window pops
up and is ready for use immediately when double clicked, instead of
having to look at the progress bar growing; they would like the
computer boot/shutdown process to be as short as a snap instead of
minutes; ...

So, we know that one of the main aspects of desktop user experience is
"real-time". To distinguish with other kinds of real-time, I would like
to call it "Desktop Real-Time" here, this kind of real-time is mainly
about desktop user experience.

There are a couple of issues can be discussed regarding as desktop real-time:

- Multi-media applications' performance, such as audio/video play and record.

- Application start-up speed.

- GUI operations, like mouse movement, window switch, window resize/move, etc.

- System boot & shutdown time.

- Switch time between power management levels,  for example, suspend to
disk from full power level, resume to full power from sleep level, etc.

- etc.

All of the above issues impact desktop user experience. Users,
including me, will be very happy if the above issues can be solved.

There are mainly three ways to improve the real-time feature:
- Improve the hardware executing speed, such as CPU speed, I/O speed, etc.
- Improve the application performance by optimizing each of the application code
- Improve the resource management framework to make use of the system
hardwares as reasonable as possible. The word "reasonable" here means,
system should assign the hardware resources to the applications which
impact real-time feature most at the moment. There are several things
need to be done to reach such an aim:

  • Improve the OS scheduling infrastructure, such as processor
    schedulers, application virtualization mechanisms (e.g., zones), etc.
  • Create configuration tools for users to conveniently configure
    the applications that they want them to be real-time. For example, to
    set a high scheduling priority for a most often used application.
  • Pre-load some applications from disk to system memory or some
    kinds of caches. This will impact the real-time feature significantly
    because the disk I/O is usually the bottle neck.
The first two ways are up to the computer hardware vendors and
application vendors. The third way mainly depends on operating system
vendors, sometimes, also depends on infrastructure hardware vendors.
Apparently, people are always trying their best to improve real-time
feature in the first two ways, there are a lot of issues can be
discussed in the detail technologies. I personally am more interested
in the third way, I am now working on it for Solaris OS in my spare
time. Hope there will be any progress soon.

Sunday Jun 24, 2007

USB Documents: for Solaris users and driver developers

I collected some useful links for Solaris USB users and driver developers as following. For ease of use, they are grouped into classes. Most of them are frequently updated and quite up to date. Before I put them here, I sent them to my colleagues, so you can also find them posted on some opensolaris forums by others.

 
USB overview
=================

  1. Solaris USB FAQ
  2. Lists of USB devices verified on Solaris
  3. USB in the future -- Wireless USB technology


Using USB devices on Solaris
=============================

  1. Use USB devices on Solaris 10
  2. Use USB devices on Solaris Express
  3. Use USB printers on Solaris 10
  4. USB Security Script for USB device access control


Develop USB device drivers
===========================

  1. Develop USB drivers on Solaris
  2. USB project page on opensolaris.org
  3. Documents for USB driver development on Solaris


Mail lists for Solaris USB user/developers
============================================

  • usb-help@sun.com
  • driver-usb@opensolaris.org
  • driver-discuss@opensolaris.org
  • wusb-discuss@opensolaris.org

About

Colin Zou is a software engineer enjoying improving operating systems. Besides sitting at a computer all day like a dull boy, he also likes hiking and the activities on the beach.

Search

Categories
Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today