[RFC] Disk shock protection (revisited)

Hi all, at the moment I'm having another go at trying to make the disk shock protection patch fit for upstream submission. However, there are still some fundamental issues I'd like to discuss in order to make sure that I'm heading in the right direction. The general idea: A daemon running in user

Re: [RFC] Disk shock protection (revisited)

Jeff Garzik <[EMAIL PROTECTED]> wrote: > Elias Oltmanns wrote: >> The general idea: A daemon running in user space monitors input data >> from an accelerometer. When the daemon detects a critical condition, >> i.e., a sudden acceleration (for instance, laptop slides o

Re: is there any Hard-disk shock-protection for 2.6.18 and above?

Hi Pavel, Pavel Machek <[EMAIL PROTECTED]> wrote: > Hi1 > >> >> >> +module_param_named(protect_method, libata_protect_method, int, 0444); >> >> >> +MODULE_PARM_DESC(protect_method, "hdaps disk protection method >> >> >> (0=autodetect, 1=unload, 2=standby)"); >> >> > >> >> > Should this be config

Re: is there any Hard-disk shock-protection for 2.6.18 and above?

Hi Jens, Elias Oltmanns <[EMAIL PROTECTED]> wrote: > So, here is a patch in which your remarks and suggestions have been > incorporated. Additionally, I've added the requested kernel doc file > and another sysfs attribute called protect_method. The usage of this > at

Re: is there any Hard-disk shock-protection for 2.6.18 and above?

be made, for instance, in a udev rule during device setup. So, here is a patch in which your remarks and suggestions have been incorporated. Additionally, I've added the requested kernel doc file and another sysfs attribute called protect_method. The usage of this attribute is described

Re: is there any Hard-disk shock-protection for 2.6.18 and above?

Hi Pavel, thanks a lot for your first review. See comments below. Pavel Machek <[EMAIL PROTECTED]> wrote: > Hi! > [...] >> Here is a short description of what the patch does in its current >> shape: >> >> 1. Adds functions to ide-disk.c and scsi_lib.c that issue an idle >>immediate with head

Re: is there any Hard-disk shock-protection for 2.6.18 and above?

Jens Axboe <[EMAIL PROTECTED]> wrote: > On Tue, Nov 21 2006, Pavel Machek wrote: >> Hi! >> [...] >> > After some googeling and digging in gamne i read that someone said that >> > there are plans for some generic support for HD-parking in the kernel >> > and thus making such patches obsolete. [...]

Re: [PATCH] IDE: typo in ide-io.c leads to faulty assignment

"Jesper Juhl" <[EMAIL PROTECTED]> wrote: > These two lines : > > - args->handler = task_no_data_intr; > + args->handler = &task_no_data_intr; > > do the same thing. Thanks for explaining, obviously I got a bit confused. Sorry for the noise. Elias - To unsubscribe from thi

[PATCH] IDE: typo in ide-io.c leads to faulty assignment

Due to a typo in ide_start_power_step, the result of a function rather than its pointer is assigned to args->handler. The patch applies to 2.6.19-rc6 but the problem exists in the stable branch as well. Signed-off-by: Elias Oltmanns <[EMAIL PROTECTED]> --- diff --git a/drivers/ide/i

[OT] Character representation in video ram when using unicode font

Hi all, very sorry for bothering you with this question but I didn't know a better place to post it to. My problem is this: As I understand, I can load a fixed unicode font with either 256 or 512 different characters into video rom. Now, I'd like to know how the slots and their attributes are repr

patch - ftdi_sio.c floods my logs with "write request of 0 bytes"

Hi there, unfortunately, I'm everything else but a developer, so please be a bit patient with me. As indicated by the subject, I got annoyed by the error message mentioned flooding my log files. Comparing ftdi_sio.c to some of the other usb->serial converter drivers, I decided to apply the follow