There is already a suite HRT of tests they include a nanosleep jitter
test with 8 or 9 other tests..
find them inside the hrt-support patch at http://high-res-timer.sf.net
Daniel
On Wed, 2005-08-31 at 11:01 -0400, Steven Rostedt wrote:
> Thomas,
>
> I just was wondering how the HR Timers were
* Greg KH ([EMAIL PROTECTED]) wrote:
> On Wed, Aug 24, 2005 at 06:20:33PM -0700, Chris Wright wrote:
> > Now that capability functions are default, rootplug no longer needs to
> > manually add them to its security_ops.
> >
> > Cc: Greg Kroah <[EMAIL PROTECTED]>
> > Signed-off-by: Chris Wright <[EM
On Wed, 2005-08-31 at 00:35, Ingo Molnar wrote:
> * Fernando Lopez-Lezcano <[EMAIL PROTECTED]> wrote:
>
> > Do a "tar cvf usr.tar /usr" just to read/write a lot to disk (this
> > within the same SATA disk). Watch memory being used in a system
> > monitor applet up to 100%. After a while, hard to
On Wed, 31 Aug 2005, Martin J. Bligh wrote:
> --Hugh Dickins <[EMAIL PROTECTED]> wrote (on Wednesday, August 31, 2005
> 14:42:38 +0100):
> >
> > Which is indeed a further disincentive against shared page tables.
>
> Or shared pagetables a disincentive to randomizing the mmap space ;-)
Fair poin
Thomas,
I just was wondering how the HR Timers were in the latest -rtX patch and
wrote my own little jitter test using nanosleep. Here's the results:
On vanilla 2.6.13-rc7-git1 (Yes I need to get over to 2.6.13)
# ./jitter
starting calibrate
finished calibrate: 2133.9060MHz 2133906034
time sle
We have noticed when changing from kernel 2.4.23 to 2.6.8 that
timestamps of files are not changed if opened for a write and nothing is
written. When using 2.4.23 timestamps are changed. When using a local
filesystem (reiserfs) with either kernel, timestamps are changed.
Symptoms vary with the cl
[ Putting everyone cc again and leaving maciej's reply intact for
reference ]
Maciej W. Rozycki wrote:
The ID is 0x14 for Intel. But that is wrong for AMD CPUs. The actual Dual-Core
Why can't hw designers ever get such things right? Sigh...
Athlon CPUs we have report an APIC version of
> > Which is indeed a further disincentive against shared page tables.
>
> Or shared pagetables a disincentive to randomizing the mmap space ;-)
> They're incompatible, but you could be left to choose one or the other
> via config option.
>
> 3% on "a certain industry-standard database benchmark
On Wednesday 31 August 2005 15:13, Martin Wilck wrote:
> In other words: What would be broken if we just used an APIC ID mask of
> 0xFF everywhere?
Nothing I think. It's more historical reasons. The physflat subarchitecture
patch essentially removed it, but it needs some rework and merging
with
On Mon, Aug 29, 2005 at 11:23:39PM +0200, Andi Kleen wrote:
> Tom Rini <[EMAIL PROTECTED]> writes:
>
> > This adds hardware breakpoint support for i386. This is not as well tested
> > as
> > software breakpoints, but in some minimal testing appears to be functional.
>
> This really would need s
Jim McCloskey wrote:
When I try to compile 2.6.13, using a complete tarball from
kernel.org, the compilation fails with:
---
SYSMAP System.map
SYSMAP .tmp_System.map
Inconsistent kallsyms data
Try setting CONFIG_KALLSYMS_EXTRA_PASS
ma
On Wed, 31 Aug 2005, Alan Cox wrote:
Registering means to create an ID for the system? Something out of
timestamp plus your PCI IDs and CPU info and so on?
Or have the other end issue you some kind of secure cookie, which was my
thought. Generating it locally as you suggest would be even bette
On Wed, Aug 31, 2005 at 09:20:17AM +0200, Ingo Molnar wrote:
>
> * Daniel Walker <[EMAIL PROTECTED]> wrote:
>
> > Ingo,
> > This patch adds a vermagic hook so PREEMPT_RT modules can be
> > distinguished from PREEMPT_DESKTOP modules.
>
> vermagic is very crude and there are zillions of other
--Hugh Dickins <[EMAIL PROTECTED]> wrote (on Wednesday, August 31, 2005
14:42:38 +0100):
> On Wed, 31 Aug 2005, Arjan van de Ven wrote:
>> On Wed, 2005-08-31 at 12:44 +0100, Hugh Dickins wrote:
>> > I was going to say, doesn't randomize_va_space take away the rest of
>> > the point? But no, it a
Hi Maciej,
It actually depends on the APIC type, rather than the CPU. E.g. with
Pentium systems the width of the ID is either 4 bits or 8 bits,
depending on whether the integrated or an external 82489DX APIC is
used. This should be able to be determined by the APIC version; for
v <= 0xf the ID
* Holger Kiehl ([EMAIL PROTECTED]) wrote:
> On Wed, 31 Aug 2005, Jens Axboe wrote:
>
> Full vmstat session can be found under:
Have you got iostat? iostat -x 10 might be interesting to see
for a period while it is going.
Dave
--
-Open up your eyes, open up your mind, open up your code
Greetings gentlemen,
please find the patch against 2.6.13 tree with Russel's proposal taken
into account.
This patch that allows passing the pointer to custom power management
routine (via platform_device) to 8250 serial driver.
Please note that the exported functions' API remained the same.
T
Jens Axboe wrote:
> On Wed, Aug 31 2005, Brian King wrote:
>
>>Jens Axboe wrote:
>>
>>>On Tue, Aug 30 2005, [EMAIL PROTECTED] wrote:
>>>
>>>
I ran across a memory leak related to the cfq scheduler. The cfq
init function increments the refcnt of the associated request_queue.
This refcou
On 8/31/05, Pekka Enberg <[EMAIL PROTECTED]> wrote:
> After finally understanding what you're doing, how about:
>
> static inline int hint_allocate(struct inode *dir)
> {
> loff_t *hints;
> int err = 0;
>
> if (!MSDOS_I(dir)->scan_hints)
Should read:
if (MSDOS_I(dir)->sc
On Wed, 31 Aug 2005, Jens Axboe wrote:
Nothing sticks out here either. There's plenty of idle time. It smells
like a driver issue. Can you try the same dd test, but read from the
drives instead? Use a bigger blocksize here, 128 or 256k.
I used the following command reading from all 8 disks in
On 8/31/05, Machida, Hiroyuki <[EMAIL PROTECTED]> wrote:
> How about this ?
>
> if (!MSDOS_I(dir)->scan_hints) {
> hints = kcalllo();
>
> down
> if (MSDOS_I(dir)->scan_hints) {
> up
> goto
On 8/31/05, Machida, Hiroyuki <[EMAIL PROTECTED]> wrote:
> > Please consider moving this check to callers. Conditional allocation
> > makes this bit strange API-wise. Or alternatively, give
> > hint_allocate() a better name.
>
> How about hint_allocate_conditional() ?
hint_get() sounds better to
On Wed, Aug 31 2005, Brian King wrote:
> Jens Axboe wrote:
> > On Tue, Aug 30 2005, [EMAIL PROTECTED] wrote:
> >
> >>I ran across a memory leak related to the cfq scheduler. The cfq
> >>init function increments the refcnt of the associated request_queue.
> >>This refcount gets decremented in cfq's
Hi,
the description of PCI_NAMES is conflicting with its default option (now
N/y/? instead of Y/n/?). Here is a small patch that should remove the
confusion in drivers/pci/Kconfig.
Regards,
Alexandre
Signed-off-by : Alexandre Buisse <[EMAIL PROTECTED]>
--- drivers/pci/Kconfig.old 2005-08-31
On Wed, 31 Aug 2005, Arjan van de Ven wrote:
> On Wed, 2005-08-31 at 12:44 +0100, Hugh Dickins wrote:
> > I was going to say, doesn't randomize_va_space take away the rest of
> > the point? But no, it appears "randomize_va_space", as it currently
> > appears in mainline anyway, is somewhat an exag
On Wed, 31 Aug 2005, Vojtech Pavlik wrote:
On Tue, Aug 30, 2005 at 08:06:21PM +, Holger Kiehl wrote:
How does one determine the PCI-X bus speed?
Usually only the card (in your case the Symbios SCSI controller) can
tell. If it does, it'll be most likely in 'dmesg'.
There is nothing in dm
Jens Axboe wrote:
> On Tue, Aug 30 2005, [EMAIL PROTECTED] wrote:
>
>>I ran across a memory leak related to the cfq scheduler. The cfq
>>init function increments the refcnt of the associated request_queue.
>>This refcount gets decremented in cfq's exit function. Since blk_cleanup_queue
>>only call
On 8/31/05, Eric Anholt <[EMAIL PROTECTED]> wrote:
> the X Render extension." No, EXA is a different acceleration
> architecture making different basic design decisions related to memory
> management and driver API.
I did start the EXA section off with this: "EXA replaces the existing
2D XAA driv
Seems patches stored on ftp://ftp.kernel.org/pub/linux/kernel/v2.6/snapshots
are empty (only logs are correct):
$ lftp ftp://ftp.kernel.org/pub/linux/kernel/v2.6/snapshots
cd ok, cwd=/pub/linux/kernel/v2.6/snapshots
lftp ftp.kernel.org:/pub/linux/kernel/v2.6/snapshots> ls patch-2.6.13-git*
-rw-r
Hi,
On Wed, 2005-08-31 at 12:35, Glauber de Oliveira Costa wrote:
> At a first look, i thought about locking gdt-related data. But in a
> closer one, it seemed to me that we're in fact modifying a little bit
> more than that in the resize code. But all these modifications seem to
> be somehow rel
Hello,
Using aoe on a sparc64 system gives strange results:
sunny:/dev/etherd# echo >discover
sunny:/dev/etherd# mke2fs e0.0
mke2fs 1.37 (21-Mar-2005)
mke2fs: File too large while trying to determine filesystem size
sunny:/dev/etherd# blockdev --getsz e0.0
-4503599627370496
The log says:
Aug 31
Pekka Enberg wrote:
On 8/31/05, Machida, Hiroyuki <[EMAIL PROTECTED]> wrote:
+inline
+static int hint_index_body(const unsigned char *name, int name_len, int
check_null)
+{
+ int i;
+ int val = 0;
+ unsigned char *p = (unsigned char *) name;
+ int id = current->pid;
+
+
On Wed, 31 Aug 2005, Martin Wilck wrote:
> We are wondering why these masks are there in the subarch code at all. After
> all, whether or not 8-bit APIC IDs are supported depends mainly on the CPU
> type used. Why wouldn't it possible to have a "default" architecture with APIC
> IDs > 15, if the C
* Srivatsa Vaddagiri <[EMAIL PROTECTED]> [050831 14:20]:
> On Wed, Aug 31, 2005 at 04:47:05PM +0530, Srivatsa Vaddagiri wrote:
> > On Wed, Aug 31, 2005 at 01:03:05PM +0200, Arjan van de Ven wrote:
> > > that sounds like a fundamental issue that really needs to be fixed
> > > first!
> >
> > It shou
Hi Andi, hi everyone,
The MP_valid_apicid() function [arch/i386/kernel/mpparse.c] checks
whether the APIC version field is >=20 in order to determine whether
the CPU supports 8-bit physical APIC ids.
Yes, it's broken. ... . Also it's only
a sanity check for broken BIOS, and in this case it cau
On Mer, 2005-08-31 at 13:52 +0100, Russell King wrote:
> The key thing is that port.dev should be set appropriately and the
> relevant calls to serial8250_suspend_port/serial8250_resume_port
> be made (or port.dev should be NULL if no power management is
> expected - in which case it may be managed
On Mer, 2005-08-31 at 01:19 +0200, Sven Ladegast wrote:
> On Wed, 31 Aug 2005, Alan Cox wrote:
>
> > "Register a box + optional PCI id list/CPU info"
> > Reply with a secured serial number
>
> Registering means to create an ID for the system? Something out of
> timestamp plus your PCI IDs and CP
Hi,
Thank you checking code...
Pekka Enberg wrote:
Hi,
:
snip
This patch enables using hint information on scanning dir.
It achieves excellent performance with "ls -l" for over 1000 entries.
* fat-dirscan-with-hint_3.patch for linux 2.6.13
fs/fat/dir.c | 130
Hi,
Pekka Enberg wrote:
Hi,
On 8/31/05, Machida, Hiroyuki <[EMAIL PROTECTED]> wrote:
+inline
+static int hint_allocate(struct inode *dir)
+{
+ loff_t *hints;
+ int err = 0;
+
+ if (!MSDOS_I(dir)->scan_hints) {
+ hints = kcalloc(FAT_SCAN_NWAY, sizeof(loff_t), GF
On Wed, Aug 31, 2005 at 02:00:24PM +0100, Alan Cox wrote:
> On Mer, 2005-08-31 at 10:33 +0100, Russell King wrote:
> > Unfortunately, it appears that some of these drivers do not contain
> > email addresses for their maintainers, neither are they listed in
> > the MAINTAINERS file. (mwavedd and se
The patch for the getprlimit() syscall:
Signed-off-by: Wieland Gmeiner <[EMAIL PROTECTED]>
---
arch/i386/kernel/syscall_table.S |1
include/asm-i386/unistd.h|3 -
include/linux/security.h | 25 ++-
kernel/sys.c | 85 +++
The patch for the setprlimit() syscall:
Signed-off-by: Wieland Gmeiner <[EMAIL PROTECTED]>
---
arch/i386/kernel/syscall_table.S |1
include/asm-i386/unistd.h|3 -
kernel/sys.c | 114 ---
security/selinux/hooks.c
Hi all!
Just for the logs, the getprlimit/setprlimit system call for the
2.6.13 plus a man page in case sombody cares.
Again my request to those who reviewed my first try, maybe you could
have a look at this if locking is better now, I do not break SELinux
anymore etc. so I can shift to the 64 Bi
Something like below, which has the advantange that there is still only
one implementation of the function
True, that´s a great advantage.
and if it's still slower, we really need to check the compiler
Please have a look at the following patch. It takes your idea of
inlining but moves
t
Phy Prabab wrote:
Hello all,
I am seeing something odd w/sockets. I have an app
that opens and closes network sockets. When the app
terminates it releases all fd (sockets) and exists,
yet running netstat after the app terminates still
shows the sockets as open! Am I doing something wrong
or i
On Mer, 2005-08-31 at 10:33 +0100, Russell King wrote:
> Unfortunately, it appears that some of these drivers do not contain
> email addresses for their maintainers, neither are they listed in
> the MAINTAINERS file. (mwavedd and serial_txx9).
I'll have a quick look at mwave. If I remember rightl
On Sun, Aug 28, 2005 Al Viro wrote:
> Signed-off-by: Al Viro <[EMAIL PROTECTED]>
I added this patch to linuxtv.org CVS.
Thanks,
Johannes
> diff -urN RC13-rc7-base/drivers/media/dvb/frontends/tda80xx.c
> current/drivers/media/dvb/frontends/tda80xx.c
> --- RC13-rc7-base/drivers/media/dvb/frontend
Holger Kiehl wrote:
3236497 total 1.4547
2507913 default_idle 52248.1875
158752 shrink_zone 43.3275
121584 copy_user_generic_c 3199.5789
34271 __wake_up_bit
On Wed, Aug 31, 2005 at 02:11:44PM +0200, Ingo Molnar wrote:
> > I recompiled and installed the kernel, but there's no change (getconf
> > ARG_MAX still gives 131072.) What am I missing?
>
> MAX_ARG_PAGES should work just fine. I think the 'getconf ARG_MAX'
> output is hardcoded. (because the k
On 8/31/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> Hi everyone:
>
> I am implemnting one ioctl() in one character device.
>
> That need know instruction pointer of user space. I am on i386
> platform.
> I can sure I am in process context. and enter kernel by system call way.
>
>
On Wed, Aug 24, 2005 Philipp Matthias Hahn wrote:
> Integrate saa7146_i2c adapter into device model:
> Moves entries from /sys/device/platform to /sys/device/pci*.
>
> Signed-off-by: Philipp Hahn <[EMAIL PROTECTED]>
I added this patch to linuxtv.org CVS.
Thanks,
Johannes
> --- linux/drivers/me
Hi,
-rc6-mm2 breaks USB unplug for me. Happens with every USB device,
gcc-3.3.5 and gcc-3.4.4 as well as preempt and non-preempt and is 100%
reproducible.
-rc6-mm1 seems fine.
Reverting the following part of
driver-core-fix-bus_rescan_devices-race.patch
fixes this for me:
diff -puN drivers/base/
* Nick Matteo <[EMAIL PROTECTED]> wrote:
> The other day I was running a grep on a big directory tree and got a
> "Argument list too long" error. Since I'd like to have this work
> without messing with find and xargs each time, I went into
> include/linux/binfmts.h and changed
>
> #define MA
On Wed, Aug 31 2005, Holger Kiehl wrote:
> >>>Ok, I did run the following dd command in different combinations:
> >>>
> >>> dd if=/dev/zero of=/dev/sd?1 bs=4k count=500
> >>
> >>I think a bs of 4k is way too small and will cause huge CPU overhead.
> >>Can you try with something like 4M? Also,
Ingo Molnar <[EMAIL PROTECTED]> writes:
> - if everything fails and automatic latency tracing does not show
> anything out of ordinary, then you could try to do "user-triggered
> tracing" of jackd's critical path. This is more laborous to do, but
> should pinpoint the latency reason in a p
On Tue, Aug 30, 2005 at 10:45:54PM +0200, Jesper Juhl wrote:
>
> I've posted similar patches in the past, but was asked to first until the
> short-circuit patch moved from -mm to mainline - and since it is now
> firmly there in 2.6.13 I assume there's no problem there anymore.
> I was also asked
Nathan Becker wrote:
I would be happy to post my exact C source that I use to do the
benchmark, but I wanted to get some feedback first in case I'm just
doing something stupid. Also, since I'm not subscribed to this list,
please cc me directly regarding this topic.
Hi Nathan,
Cache issu
On Wed, 31 Aug 2005, Jens Axboe wrote:
On Wed, Aug 31 2005, Vojtech Pavlik wrote:
On Tue, Aug 30, 2005 at 08:06:21PM +, Holger Kiehl wrote:
How does one determine the PCI-X bus speed?
Usually only the card (in your case the Symbios SCSI controller) can
tell. If it does, it'll be most lik
On Wed, 2005-08-31 at 12:44 +0100, Hugh Dickins wrote:
> I was going to say, doesn't randomize_va_space take away the rest of
> the point? But no, it appears "randomize_va_space", as it currently
> appears in mainline anyway, is somewhat an exaggeration: it just shifts
> the stack a little, with n
On Tue, 30 Aug 2005, Dave McCracken wrote:
>
> This patch implements page table sharing for all shared memory regions that
> span an entire page table page. It supports sharing at multiple page
> levels, depending on the architecture.
>
> Performance testing has shown no degradation with this pa
Jiri Slaby wrote:
+static struct pci_device_id mv_pci_tbl[] = {
+{PCI_DEVICE(PCI_VENDOR_ID_MARVELL, 0x5040), 0, 0, chip_504x},
+{PCI_DEVICE(PCI_VENDOR_ID_MARVELL, 0x5041), 0, 0, chip_504x},
+{PCI_DEVICE(PCI_VENDOR_ID_MARVELL, 0x5080), 0, 0, chip_508x},
+{PCI_DEVICE(PCI_VENDOR_ID_M
Yes, that's also something I was thinking of, but I wasn't sure enough
in this radical change :)
Anyway, I do agree that this way looks better than the current one.
So, if you don't object against other changes (say, the suggested
approach to set uart->pm), I can proceed with the changes you sug
>
> The two different uses of the superblock lock are really quite
> different; I don't see any particular problem with using two different
> locks for the two different things. Mount and the namespace code are
> not locking the same thing --- the fact that the resize code uses the
> superblock l
On Wed, Aug 31, 2005 at 03:10:09PM +0400, Vitaly Wool wrote:
> please find the patch that allows passing the pointer to custom power
> management routine (via platform_device) to 8250 serial driver.
> Please note that the interface to the outer world (i. e. exported
> functions) remained the same
Sorry for format. Attached is the better one :)
Vitaly Wool wrote:
Greetings,
please find the patch that allows passing the pointer to custom power
management routine (via platform_device) to 8250 serial driver.
Please note that the interface to the outer world (i. e. exported
functions) rema
On Wed, Aug 31, 2005 at 04:47:05PM +0530, Srivatsa Vaddagiri wrote:
> On Wed, Aug 31, 2005 at 01:03:05PM +0200, Arjan van de Ven wrote:
> > that sounds like a fundamental issue that really needs to be fixed
> > first!
>
> It should be fixed by the patch here:
> http://marc.theaimsgroup.com/?l=linu
On Wed, Aug 31, 2005 at 01:03:05PM +0200, Arjan van de Ven wrote:
> that sounds like a fundamental issue that really needs to be fixed
> first!
It should be fixed by the patch here:
http://marc.theaimsgroup.com/?l=linux-kernel&m=111556608901657&w=2
Tony,
I don't see any slow bootups on x8
On Wed, Aug 31 2005, Erik Mouw wrote:
> On Wed, Aug 31, 2005 at 10:07:45AM +0200, Jens Axboe wrote:
> > On Mon, Aug 29 2005, Erik Mouw wrote:
> > > There are four prerequisites for direct IO:
> > > - the file needs to be opened with O_DIRECT
> > > - the buffer needs to be page aligned (hint: use ge
On Wed, Aug 31, 2005 at 10:07:45AM +0200, Jens Axboe wrote:
> On Mon, Aug 29 2005, Erik Mouw wrote:
> > There are four prerequisites for direct IO:
> > - the file needs to be opened with O_DIRECT
> > - the buffer needs to be page aligned (hint: use getpagesize() instead
> > of assuming that a pag
Greetings,
please find the patch that allows passing the pointer to custom power
management routine (via platform_device) to 8250 serial driver.
Please note that the interface to the outer world (i. e. exported
functions) remained the same.
Best regards,
Vitaly
Currently 8250 serial driver d
> > ehh
> > why does it cause slow boots?
> > if that kind of behavior changes... isn't that a sign there is a
> > fundamental bug still ?
>
> Well it seems like the next_timer_interrupt is something like 400
> jiffies away and RCU code waits for completion for example in the
> network code.
th
Hi Grigory,
it's unclear from your letter where you take pnx4008_uart_pm from. Can
you please elaborate?
What I would think of if I were you is adding a field 'pm' to struct
plat_serial8250_port which is filled in in the architecture-specific
part and setting up->pm accrodingly.
I'll send a
On Wed, Aug 31, 2005 at 01:34:03PM +0300, Tony Lindgren wrote:
> Well it seems like the next_timer_interrupt is something like 400
> jiffies away and RCU code waits for completion for example in the
> network code.
I had a patch to fix the problem of "RCU grace period extended
because of sleeping
Brett Russ napsal(a):
This is the first public release of my libata compatible low level driver for
the Marvell SATA family. Currently it successfully runs in PIO mode on a 6081
chip. EDMA support is in the works and should be done shortly. Review,
testing (especially on other flavors of Marv
* Arjan van de Ven <[EMAIL PROTECTED]> [050831 11:40]:
> On Wed, 2005-08-31 at 10:44 +0300, Tony Lindgren wrote:
> > * Alistair John Strachan <[EMAIL PROTECTED]> [050830 18:57]:
> > > On Tuesday 30 August 2005 13:31, Tony Lindgren wrote:
> > > [snip]
> > > > >
> > > > > Same issue, it's waiting on
Denis Vlasenko <[EMAIL PROTECTED]> wrote:
-> What it can do? In particular, can it:
-> * send packets with arbitrary contents? In particular, packets
-> shorter than 3-address 802.11 header? packets with WEP bit set?
-> Does it allow to do WEP encoding by host instead of hal?
-> Any weird lim
Florian Weimer <[EMAIL PROTECTED]> wrote:
-> > the problem with openbsd version of the hal is that it is - sorry to
-> > say that - fundamentally broken, at least it was last time I was
-> > checking.
->
-> It's better than nothing, that is, it worked for us when we gave it a
-> try. And it se
On Wed, Aug 31, 2005 at 12:16:10PM +0200, Jan-Benedict Glaw wrote:
> On Wed, 2005-08-31 11:10:48 +0100, Russell King <[EMAIL PROTECTED]> wrote:
> > On Thu, Aug 25, 2005 at 01:20:45PM +0100, Rahul Tank wrote:
> > > I am a newbee tryinging for serial port
> > > multiplexing. Currently my driver s
On Wed, 2005-08-31 11:10:48 +0100, Russell King <[EMAIL PROTECTED]> wrote:
> On Thu, Aug 25, 2005 at 01:20:45PM +0100, Rahul Tank wrote:
> > I am a newbee tryinging for serial port
> > multiplexing. Currently my driver supports for one
> > port
> > (/dev/ttyS0). However i want to use the same p
Hi,
On 8/31/05, Machida, Hiroyuki <[EMAIL PROTECTED]> wrote:
>
> Sorry, I send out wrong version. I attached the latest patch to 2.6.13.
>
> OGAWA Hirofumi wrote:
> > "Machida, Hiroyuki" <[EMAIL PROTECTED]> writes:
> >
> >
> >>Here is a revised version of dirent scan patch, mentioned at
> >>fol
On Thu, Aug 25, 2005 at 01:20:45PM +0100, Rahul Tank wrote:
> I am a newbee tryinging for serial port
> multiplexing. Currently my driver supports for one
> port
> (/dev/ttyS0). However i want to use the same physical
> port for 2 virtual ports.I am NOT sending two type of
> data simultaneously
On Mon, Aug 29, 2005 at 09:55:04PM +0400, Grigory Tolstolytkin wrote:
> I'm working on power management support for a particular ARM based board
> and I've got a question:
> I want to add a board specific power management for standard uart driver
> (serial8250). For this purpose there is a specia
On 8/31/05, Machida, Hiroyuki <[EMAIL PROTECTED]> wrote:
> +inline
> +static int hint_index_body(const unsigned char *name, int name_len, int
> check_null)
> +{
> + int i;
> + int val = 0;
> + unsigned char *p = (unsigned char *) name;
> + int id = current->pid;
> +
> +
Hi,
On 8/31/05, Machida, Hiroyuki <[EMAIL PROTECTED]> wrote:
> +inline
> +static int hint_allocate(struct inode *dir)
> +{
> + loff_t *hints;
> + int err = 0;
> +
> + if (!MSDOS_I(dir)->scan_hints) {
> + hints = kcalloc(FAT_SCAN_NWAY, sizeof(loff_t), GFP_KERNEL);
>
Stephen Hemminger wrote:
You have a version of the Marvell Yukon that was affected
by a fix in 2.6.13.
skge addr 0xfeaf8000 irq 19 chip Yukon-Lite rev 9
Both the skge and sk98lin driver were fixed to check for this.
Without the fix, the chip will be in the wrong power mode.
The version
As per the feature-removal.txt file, I will be removing the following
functions shortly:
* register_serial
* unregister_serial
* uart_register_port
* uart_unregister_port
However, there are still some drivers which use these functions:
drivers/char/mwave/mwavedd.c
On Wednesday 31 August 2005 11:16, Mateusz Berezecki wrote:
> Florian Weimer <[EMAIL PROTECTED]> wrote:
> -> The FTC issues are shared by many (most?) wireless drivers. The
> -> copyright/trade secret issues might be worked around by basing the
> -> work on the OpenBSD version of that driver (and
On Wed, 2005-08-31 at 10:44 +0300, Tony Lindgren wrote:
> * Alistair John Strachan <[EMAIL PROTECTED]> [050830 18:57]:
> > On Tuesday 30 August 2005 13:31, Tony Lindgren wrote:
> > [snip]
> > > >
> > > > Same issue, it's waiting on dynticks before being reworked.
> > >
> > > Also one more minor iss
* Mateusz Berezecki:
> Florian Weimer <[EMAIL PROTECTED]> wrote:
> -> The FTC issues are shared by many (most?) wireless drivers. The
> -> copyright/trade secret issues might be worked around by basing the
> -> work on the OpenBSD version of that driver (and someone is actually
> -> working on th
Sorry, I send out wrong version. I attached the latest patch to 2.6.13.
OGAWA Hirofumi wrote:
"Machida, Hiroyuki" <[EMAIL PROTECTED]> writes:
Here is a revised version of dirent scan patch, mentioned at
following E-mail.
This patch addresses performance damages on "ls | xargs xxx" and
reve
i have no freaking idea of coding. but going throught this "Discuss
issues related to the xorg tree" talk, made me feel and say "mommy
(coder), daddy (admin), please dont fight you tearing
us(users) apart."
glad its worked out.. all i hope is we(users) , now , get some nice
fast xorg :D.
Florian Weimer <[EMAIL PROTECTED]> wrote:
-> The FTC issues are shared by many (most?) wireless drivers. The
-> copyright/trade secret issues might be worked around by basing the
-> work on the OpenBSD version of that driver (and someone is actually
-> working on that).
the problem with openbsd
On Mon, Aug 29 2005, Erik Mouw wrote:
> There are four prerequisites for direct IO:
> - the file needs to be opened with O_DIRECT
> - the buffer needs to be page aligned (hint: use getpagesize() instead
> of assuming that a page is 4k
> - reads and writes need to happen *in* multiples of the soft
Chris Wright ([EMAIL PROTECTED]) wrote:
> * David Härdeman ([EMAIL PROTECTED]) wrote:
> > I'm currently playing around with the security/root_plug.c LSM module
> you'll have better luck on the lsm list
Thanks for the pointer
> > 1) What's the recommended way of telling that someone is logging in
--- David Brownell <[EMAIL PROTECTED]> wrote:
> The last couple times SPI frameworks came up here,
> some of the feedback
> included "make it use the driver model properly;
> don't be like I2C".
>
> In hopes that it'll be useful, here's a small SPI
> core with driver model
> support driven from
Alan Cox wrote:
On Llu, 2005-08-29 at 11:54 +0800, qiyong wrote:
We can ignore it safely. sys_promote is a different approach from
selinux. sys_promote is to let sysadmin manually manipulate a running
process,
You can ignore the patch easily enough. Ignoring the locking doesn't
wor
* Jeff Garzik:
> There is still the open question of whether this is legal enough to
> include in the kernel :(
Are you referring to FTC issues, or potential copyright/trade secret
issues?
The FTC issues are shared by many (most?) wireless drivers. The
copyright/trade secret issues might be wo
Ulrich Drepper wrote:
On 8/29/05, Alan Cox <[EMAIL PROTECTED]> wrote:
Fixing it might be useful in some obscure cases anyway - POSIX threads
might benefit from it too, providing the functionality of changing all
thread uids at once isnt triggered for sensible threaded app behaviour.
I
Hi, I am trying to do a small amount of work on the wcfxo device driver
(or an fxo card), which is part of zapatel, which is used by asterisk,
the linux open source PBX (hence cross post).
question 1: Are PCI Master Aborts delivered to all subsystems, if they
are, do I need to "fix" ALL the dr
* Alistair John Strachan <[EMAIL PROTECTED]> [050830 18:57]:
> On Tuesday 30 August 2005 13:31, Tony Lindgren wrote:
> [snip]
> > >
> > > Same issue, it's waiting on dynticks before being reworked.
> >
> > Also one more minor issue; Dyntick can cause slow boots with dyntick
> > enabled from boot be
201 - 300 of 317 matches
Mail list logo
