* Feedback
@ 2016-06-04 12:43 Salah Triki
2016-06-04 16:37 ` Feedback Greg KH
0 siblings, 1 reply; 6+ messages in thread
From: Salah Triki @ 2016-06-04 12:43 UTC (permalink / raw)
To: gregkh; +Cc: jerry-chuang, driverdev-devel, salah.triki
Hi Greg,
I sent you, on May 4, a patchset entitled '[PATCH V6 0/9] staging: rtl8192u:
Checking return value/propagating errors', and it not included in
4.7-rc1! Should I resend the patchset ?
best regards,
salah triki
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Feedback
2016-06-04 12:43 Feedback Salah Triki
@ 2016-06-04 16:37 ` Greg KH
0 siblings, 0 replies; 6+ messages in thread
From: Greg KH @ 2016-06-04 16:37 UTC (permalink / raw)
To: Salah Triki; +Cc: jerry-chuang, driverdev-devel
On Sat, Jun 04, 2016 at 01:43:16PM +0100, Salah Triki wrote:
> Hi Greg,
>
> I sent you, on May 4, a patchset entitled '[PATCH V6 0/9] staging: rtl8192u:
> Checking return value/propagating errors', and it not included in
> 4.7-rc1! Should I resend the patchset ?
>
It's still in my queue, it missed the merge window for 4.7-rc1, and
should be picked up soon. Please realize that staging patches are at
the bottom of my priority queue, for obvious reasons.
thanks,
greg k-h
_______________________________________________
devel mailing list
devel@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
^ permalink raw reply [flat|nested] 6+ messages in thread
* feedback
@ 2016-05-15 19:18 Salah Triki
2016-05-16 2:44 ` feedback Greg KH
0 siblings, 1 reply; 6+ messages in thread
From: Salah Triki @ 2016-05-15 19:18 UTC (permalink / raw)
To: gregkh; +Cc: salah.triki, driverdev-devel
Hi Greg,
I sent you, on May 4, a patchset entitled '[PATCH V6 0/9] staging: rtl8192u:
Checking return value/propagating errors', and I don't get any feedbacks.
Should I resend you the patchset ?
best regards,
salah triki
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: feedback
2016-05-15 19:18 feedback Salah Triki
@ 2016-05-16 2:44 ` Greg KH
0 siblings, 0 replies; 6+ messages in thread
From: Greg KH @ 2016-05-16 2:44 UTC (permalink / raw)
To: Salah Triki; +Cc: driverdev-devel
On Sun, May 15, 2016 at 08:18:44PM +0100, Salah Triki wrote:
> Hi Greg,
>
> I sent you, on May 4, a patchset entitled '[PATCH V6 0/9] staging: rtl8192u:
> Checking return value/propagating errors', and I don't get any feedbacks.
> Should I resend you the patchset ?
It's in my queue, I'll get to them once 4.7-rc1 is out at the latest.
thanks,
greg k-h
_______________________________________________
devel mailing list
devel@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
^ permalink raw reply [flat|nested] 6+ messages in thread
* Feedback (fwd)
@ 2005-05-19 6:23 frodol
2005-05-19 6:23 ` feedback Peter Christy
2005-05-19 6:23 ` Feedback Peter Georgiev
0 siblings, 2 replies; 6+ messages in thread
From: frodol @ 2005-05-19 6:23 UTC (permalink / raw)
To: lm-sensors
Pepe Herrera wrote:
From ppherrera@supercable.es Sat Mar 23 11:25:04 2002
Received: by morannon.frodo.local (8.11.3/8.11.3) id g2NAP4d05095 ; Sat, 23 Mar 2002 11:25:04 +0100
Return-Path: <ppherrera@supercable.es>
Received: from pop3.dds.nl [213.196.1.121]
by localhost with POP3 (fetchmail-5.4.4)
for frodo@localhost (single-drop); Sat, 23 Mar 2002 11:25:04 +0100 (CET)
Received: (qmail 4819 invoked from network); 23 Mar 2002 10:07:07 -0000
Received: from unknown (HELO smtp.supercable.es) ([212.79.128.148]) (envelope-sender <ppherrera@supercable.es>)
by arkanoid.cybercomm.nl (qmail-ldap-1.03) with SMTP
for <frodol@dds.nl>; 23 Mar 2002 10:07:07 -0000
Received: from there (cliente-217216147132.cm128.conpb.supercable.es [217.216.147.132])
by smtp.supercable.es (Switch-2.0.1/Switch-2.0.1) with SMTP id g2NA83Y12582
for <frodol@dds.nl>; Sat, 23 Mar 2002 11:08:03 +0100 (MET)
Message-Id: <200203231008.g2NA83Y12582@smtp.supercable.es>
Content-Type: text/plain;
charset="iso-8859-1"
From: Pepe Herrera <ppherrera@supercable.es>
Reply-To: ppherrera@supercable.es
To: frodol@dds.nl
Subject: Feedback
Date: Sat, 23 Mar 2002 11:20:28 +0100
X-Mailer: KMail [version 1.3.1]
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Frodo:
I don't speak english well, and this e-mail can be telegraphic. I hope you
understand me:
I have a problem, in the system logs I read:
kernel: i2c-amd756.o: SMBus collision!
kernel: i2c-amd756.o: Busy wait timeout! (0800)
and them
I have a 7IX mother board and a AMD Athlon processor 500 Mhz
When the problem occurs a have run Gkrellm whit the sensors running.
The kernel version is linux-2.4.18, and the driver is instaled in
/usr/src/linux-2.4.18/drivers/i2c/i2c-amd756.o
After this problem occurs, i see:
# lsmod
Module Size Used by
agpgart 29696 3 (autoclean)
NVdriver 946400 10 (autoclean)
i2c-amd756 3248 0 (unused)
w83781d 17424 1
i2c-dev 3616 0 (unused)
eeprom 3072 0
i2c-proc 6256 1 [w83781d eeprom]
i2c-core 13248 0 [i2c-amd756 w83781d i2c-dev eeprom i2c-proc]
es1371 25920 3
ac97_codec 9376 0 [es1371]
lp 6080 0
parport_pc 14672 2
parport 24736 2 [lp parport_pc]
ipchains 41280 4
8139too 13264 1 (autoclean)
mii 1072 0 (autoclean) [8139too]
ide-cd 26496 0
cdrom 27488 0 [ide-cd]
ide-scsi 7664 0
You can help me? You need some data more?
Thanks.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE8nFb1zh9wrXFT3+URAuXKAKCKJYMi9v/RhXQTNNZKi3Zneo2rCgCeKeLB
wtVanZL51SPscwvyjnLh68s=UsrF
-----END PGP SIGNATURE-----
--
Frodo Looijaard <frodol@dds.nl> PGP key and more: http://huizen.dds.nl/~frodol
Defenestration n. (formal or joc.):
The act of removing Windows from your computer in disgust, usually followed
by the installation of Linux or some other Unix-like operating system.
^ permalink raw reply [flat|nested] 6+ messages in thread* feedback
2005-05-19 6:23 Feedback (fwd) frodol
@ 2005-05-19 6:23 ` Peter Christy
2005-05-19 6:23 ` Feedback Peter Georgiev
1 sibling, 0 replies; 6+ messages in thread
From: Peter Christy @ 2005-05-19 6:23 UTC (permalink / raw)
To: lm-sensors
Feedback regarding lm_sensors.
(pls forgive me if I've sent this to the wrong address, but this one seemed
the most appropriate)
I've just installed the latest lm_sensors packages (i2c-2.7.0 and
lm_sensors-2.7.0) on three machines (from ancient to modern) and think that
the following feedback may be of general interest.
All the machines are running freshly compiled 2.4.20 kernels, and lm_sensors
was installed using method (1) (seperate from kernel)
###############################################################################
Starting with the oldest machine first:
Motherboard: Asus P5AB
Chipset: Ali V
Processor: AMD K6-2-350 (overclocked to 400)
OS: VectorLinux 3.0 (Slackware-alike)
Sensor chip: W83781D
Modules loaded: eeprom
W8371D
i2c-proc
i2c-isa
i2c-ali15x3
i2c-core
temp1 appears to be the SYS temp
temp2 appears to be the CPU temp (slightly higher than above)
temp3 appears to be MB/ambient case (?) temp
I had to tweak the suggested w83781d temperature limits to reflect the above
order....
fan2 appears to be CPU fan (probably depends on which connector fan is
connected to...)
The in2 ("3.3v") readings appear slightly anomolous, reading higher than the
"VID" voltage, and slightly higher than that reported by the BIOS - enough to
trigger the alarm. Assuming the BIOS to be right, I have widened the limits
from 5% to 10% as a stop-gap measure. (The machine has functioned perfectly
for several years, so I think I can assume its functioning within acceptable
limits!)
Installation funnies: VectorLinux is based on Slackware (which uses BSD style
init scripts) but has added a SysV init layer to "aid" compatibility. This
confused the installation detection which suggested installing a SysV (init.d)
script as well as suggesting lines to go in rc.local. You need to choose one
or the other, but not both! I went the rc.local route which worked fine.
Note: It's not enough just to put "sensors -s" in rc.local - you have to put
the full path, ie /usr/local/bin/sensors -s
###############################################################################
A more recent machine:
Motherboard: Gigabyte GA-7ZM
Chipset: VIA KT-133
Processor AMD Duron 1.2GHz
OS Slackware 9.0b
Sensor chip: Via 686a
Modules loaded: via686a
eeprom
i2c-proc
i2c-isa
i2c-viapro
i2c-core
temp1 appears to be CPU temp (highest)
temp2 appears to be SYS temp
temp3 appears to be MB/anbient case (?) temp
The suggested in0 min and max voltages seemed incorrect for this
mobo/processor combination. I reduced them from 2.0/2.5 to 1.6/2.1 to more
accurately reflect the proper values.
Sensors is called from rc.local using the full path (/usr/local/bin/sensors
-s)
This was the least problematic install of the three.
###############################################################################
The most modern (and probably interesting!) machine:
an FIC A360+ laptop (Locally re-badged as a Tiny MediaBook 1000)
Motherboard: FIC(?)
Chipset: Via 686 (No specs from FIC, or visible on boot, but its definitely
some kind of 686!)
Processor: Intel Celeron 1GHz
OS: Slackware 8.1
Sensor chip 686a-isa (?)
Note: To function correctly, this machine *must* have a recent acpi patch
applied to the kernel!
Modules loaded: via686a
i2c-proc
i2c-isa
i2c-core
temp1 and temp2 mostly report identical temperatures, so its difficult to
determine which is the cpu and which is the sys!
Both fans sensors read 0, even though (once the acpi patch is applied) the
processor fan throttles properly. (There is only one fan)
sensors-detect reported being unable to load the viapro module.
It was necessary to "modprobe via686a force_addr=0xf000" to get the via686
module to run correctly.
The full path to sensors -s needs to be added to rc.local
This one was definitely the most fiddly of the lot, not helped by the
unavailability of any significant technical info from the FIC website.
Although they have a technical specs page for this laptop, it is very sparse
and doesn't even specify the chipset used! Its possible that this machine
needs one of the "un-probeable" drivers, but I don't know how to determine
this. I seem to be getting sensible voltage and temperature readings, but it
would be nice to have some fan info as well!
As I said, forgive me if I've sent this info to the wrong address, but
hopefully you (and others) may find it useful.......
--
Pete Christy
christy@attglobal.net
^ permalink raw reply [flat|nested] 6+ messages in thread* Feedback
2005-05-19 6:23 Feedback (fwd) frodol
2005-05-19 6:23 ` feedback Peter Christy
@ 2005-05-19 6:23 ` Peter Georgiev
1 sibling, 0 replies; 6+ messages in thread
From: Peter Georgiev @ 2005-05-19 6:23 UTC (permalink / raw)
To: lm-sensors
Hiya guys,
Just dropping you a couple of lines to let you know
lm_sensors work fine with my motherboard.
Detail as follows:
Motherboard: MSI (Micro-Star International)
MS-6580 (v2.1) 845PE Max ATX
G52-M6580X4
Chipset: Intel 845PE
LM_Sensors: v2.6.5
Detected busses:i2c-i801 / i2c-isa
Detected chips: w83781d / lm80 (emulated??)
SMBus gives buggy output (lame lm80 emulation??):
lm80-i2c-0-2f
Adapter: SMBus I801 adapter at 0c00
Algorithm: Non-I2C SMBus adapter
+5V: +6.71 V (min = +6.71 V, max = +6.71 V) ALARM
VTT: +2.55 V (min = +2.55 V, max = +2.55 V) ALARM
+3.3V: +4.43 V (min = +4.43 V, max = +4.43 V) ALARM
+Vcore: +3.76 V (min = +3.76 V, max = +3.76 V) ALARM
+12V: +16.10 V (min = +16.10 V, max = +16.10 V) ALARM
-12V: -16.11 V (min = -16.11 V, max = -16.11 V) ALARM
-5V: -6.70 V (min = -6.70 V, max = -6.70 V) ALARM
fan1: 0 RPM (min = 0 RPM, div = 8) ALARM
fan2: 0 RPM (min = 0 RPM, div = 8) ALARM
temp: -1.00 ?C (hot:limit = -1?C, hysteresis = -1?C) ALARM
(os: limit = -1?C, hysteresis = -1?C) ALARM
alarms: Board temperature input (LM75) ALARM
ISA adapter data is just fine:
w83627hf-isa-0290
Adapter: ISA adapter
Algorithm: ISA algorithm
VCore 1: +1.76 V (min = +1.80 V, max = +1.98 V)
VCore 2: +1.80 V (min = +1.80 V, max = +1.98 V) ALARM
+3.3V: +3.18 V (min = +3.13 V, max = +3.45 V)
+5V: +4.99 V (min = +4.72 V, max = +5.24 V)
+12V: +11.86 V (min = +10.79 V, max = +13.19 V)
-12V: -11.62 V (min = -13.21 V, max = -10.90 V)
-5V: -5.01 V (min = -5.26 V, max = -4.76 V)
V5SB: +5.43 V (min = +4.72 V, max = +5.24 V)
VBat: +3.15 V (min = +2.40 V, max = +3.60 V)
fan1: 2812 RPM (min = 3000 RPM, div = 2)
fan2: 0 RPM (min = 3000 RPM, div = 2)
fan3: 0 RPM (min = 3000 RPM, div = 2)
temp1: +27?C (limit = +60?C) sensor thermistor temp2: +38.0?C (limit = +60?C, hysteresis =
+50?C) sensor = PII/Celeron diode temp3: +58.0?C (limit +60?C, hysteresis = +50?C) sensor = thermistor vid:
+1.900 V alarms: Chassis intrusion detection
ALARM beep_enable:
Sound alarm disabled
Well, hope this is of use
keep up the good work and stay cool
Peter
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2016-06-04 16:37 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-06-04 12:43 Feedback Salah Triki
2016-06-04 16:37 ` Feedback Greg KH
-- strict thread matches above, loose matches on Subject: below --
2016-05-15 19:18 feedback Salah Triki
2016-05-16 2:44 ` feedback Greg KH
2005-05-19 6:23 Feedback (fwd) frodol
2005-05-19 6:23 ` feedback Peter Christy
2005-05-19 6:23 ` Feedback Peter Georgiev
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.