From: Dave Olien <dmo@osdl.org>

This patch is forwarded from Jay Estabrook at HP.  I've compiled the
patch on ia32 and ia64 machines and it's good.  I also recreated
the patch so it would apply to mm5 without fuzzy offsets.
Here's Jay's summary of the patch:

Here's a very small set of patches against 2.6.0-test4 that help the
DAC960 driver compile cleaner (gets rid of warnings on Alpha) and help
it to work on some old OEM'ed DAC960 cards that were sold in our older
Alphas.

The warnings are all concerned with "conversions to different size
without cast", as pointers and longs are same size (8-bytes) but ints
are 4-bytes, on Alpha. I don't believe the change to (long) from (int)
will affect any 32-bit architectures, but those using LP64 like Alpha,
ie SPARC64 and prolly IA64, will have the warnings go away.

The change to make the oldest acceptable firmware version 2.70 instead
of 2.73 is made spcific to Alpha, since it is only those cards that
DEC OEM'ed from Mylex that would have such (as explained a bit better
in the patch itself).

From: Andrey Borzenkov <arvidjaar@mail.ru>

DAC960.c does it incorrectly (at least in 2.6.0-test4). It will create
_directory_ /dev/rd/cNdM making it impossible to create compat block device
entry with the same name.

The right thing it to create separate directory for each controller/target as 
in attached trivial patch (untested due to lack of hardware). You will need
devfsd support for this but then you will need it for cciss or cpqarray as 
well and possibly for others. Which returns us to the problem of devfsd 
maintenance ...

From: Dmitry Torokhov <dtor_core@ameritech.net>

I noticed that although timer_tsc registers cpufreq notifier to detect
frequency changes and adjust cpu_khz it does not set cyc2ns_scale.

From: Andrey Borzenkov <arvidjaar@mail.ru>

Various block drivers are currently devfs-unaware.  Andrey's patch attempts
to give them reasonable representations in devfs.


 "The attached patch suggests some possible names for non-floppy devices
  based on reading driver source.  I have to ask if these make sense.  At
  least for cciss Mandrake devfsd patch expects different names but it
  seems to be mistake (it assumes single controller always)

 "For floppy it is not as simple.  Floppy cannot use genhd and must
  create names manually; but I do not know what names are appropriate or
  expected.

 "For acsi the target/lun name may have problem of creating compat names
  (if any) by devfsd.

 "Please note that none of them created any devfs name under 2.4 as well.
   So it is not a regression ..."

From: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>

CONFIG_TIMER_CYCLONE doesn't build at present because calibrate_tsc() was
made static.

The patch fixes that up and moves all calibrate_tsc functions into a common
file, avoiding the current code duplication.

From: Vinay K Nallamothu <vinay-rc@naturesoft.net>

Fix a couple of cut-n-paste errors.

(Why on earth is a scsi driver poking at the RTC hardware?)

Damn 16-bit PCMCIA layer has no type checking. Complete crap.

to a pointer. That was a typo.

Ack'ed by Al Viro.

Fix the ## handling to work with old gcc versions (spaces around the ','
to make token boundaries work).

Convert SIEMENS R3964 tty line discipline on 2.6.0-test5 to use tty_ldisc owner
instead of explicit MOD_INC/DEC.

And fix the initializer to be a much more readable C99 one.

There is a leftover MOD_DEC_USE_COUNT intermezzo, with no matching _INC_
anywhere.

Since it sets owner on the file system operations there should be no
need for explicit module manipulation.

into home.osdl.org:/home/torvalds/v2.5/linux

Add a new cpufreq_update_policy call:

Certain cpufreq policy notifers have different needs at different times.
Thus it needs to be possible to re-evaluate an already set cpufreq policy.
Note that the cpufreq policy should only be set by one person: the user.
Not any other in-kernel code [with one exception, of course: during
booting].

From: Hiroshi Miura <miura@da-cha.org>

Intel SpeedStep driver using a BIOS SMI call.

Quoting his original announcement:

"This driver is based on the information from

1. Microsoft Windows XP Document.
we can get the SMI interface values from ax=E980/int15 BIOS call.

2. Intel SpeedStep Applet Document.(from HP.com)
http://h18007.www1.hp.com/support/files/evonotebook/us/download/10631.html
" Adds code to request transition ownership when processing
the system critical resume message. When a critical hibernate occurs,
the Applet does not receive any system level notification. The change forces
the Applet to re-acquire transition ownership upon resume from a critical hibernate. "

This is informative. This saied that  something 'ownership' call is needed on SMI
interface first.

3. Grover, Andrew's int 15h patch posted to cpufreq ml
Message-ID: <F760B14C9561B941B89469F59BA3A847E96E28@orsmsx401.jf.intel.com>
code which call BIOS to get SMI values. I included it.

4. Malik Martin's rev engineering results.
call is made with BX, CX, EDI register values.
and need signature 'ISG' when call.
find function values. bx=1(get) and bx=2(set)

5. Marc Lehmann's 'speedstep' utility,
sample of assembler code to call SMI.

6. My work.
find function to return max/min freq which system supportd. (bx=4)
more values are gotten, but I cannot understand...
find 'ownership' function value(bx=0, which is other than 1 2 4..).

ToDo(in pregress)
support governor "auto" and using smi_event call, imprement auto freqchange
feature.
test on 440BX/ZX platform.

Memo
 module parameters are override result of an int 15h/eax=E890h call.
 these parameter value are gotten from Windows XP registory."

Also includes some bugfixes, updates and workarounds from me.

NB: A lot of BIOS out there are buggy. You might want to try this driver
also with Intel's default values -- smi_cmd = 0x82 and smi_port = 0xb2

into home.osdl.org:/home/torvalds/v2.5/linux

into samba.org:/scratch/anton/tmp3

cpumask_up.h is broken. It tries to access the "mask" member although
that cpumask_t is an ulong on UP. This breaks archs which uses cpumask
functions even on UP such as s390.

We only support named initializers with one leval of naming, ie that

	.foo.bar = baz,

thing should go.  gcc-2.95 doesn't handle it (neither does sparse, I
think).

Replace such initializers with

	.foo = {
		.bar = baz,
	},

instead.

PA-RISC updates for 2.6.0-test5.

Contributions from Paul Bame, James Bottomley, Randolph Chung, Helge
Deller, Grant Grundler, LaMont Jones, Matthew Wilcox

Chas Williams fixed the compilation on SMP, so we can remove the Kconfig
annotation now and let people select it in the build again.

into home.osdl.org:/home/torvalds/v2.5/linux

into kernel.crashing.org:/home/benh/kernels/for-linus-ppc

into kernel.crashing.org:/home/benh/kernels/for-linus-ppc

into samba.org:/home/paulus/kernel/for-linus-ppc

into samba.org:/home/paulus/kernel/for-linus-ppc

This should fix all the remaining pci drivers which mark the pci device
ID tables as being discardable at run time.

This should fix all the AGP drivers.

pci_device_id tables can not and must not be marked discardable.  They
are used for as long as the driver is registered.

Use different var-names if they are non-static,
configure 4BRI like BRI cards, fixed new /proc entries,
inline declarations for common helper functions.

changed // comments to /* */

Main divas modules now may be build in-kernel.
4BRI cards are configured together with BRI cards.

fixed endianess errors in common code part.

Fixed internel list handling for modules built-in kernel.