Re: Why add the general notification queue and its sources

Hi, On Thu, Sep 5, 2019 at 2:37 PM Steven Whitehouse wrote: > The original reason for the mount notification mechanism was so that we > are able to provide information to GUIs and similar filesystem and > storage management tools, matching the state of the filesystem with the > state of the

Re: [RFC PATCH v2 00/13] Kernel based bootsplash

Hi, On Wed, Dec 20, 2017 at 11:44 AM Max Staudt wrote: > It'd be nice to see this bug fixed, as it happens only occasionally (as is > the nature of a > race condition), and was thus really hard to debug. I'm sure it can drive > people insane, > as they try to find out whether

Re: [RFC PATCH v2 00/13] Kernel based bootsplash

Hi, On Wed, Dec 20, 2017 at 11:44 AM Max Staudt wrote: > It'd be nice to see this bug fixed, as it happens only occasionally (as is > the nature of a > race condition), and was thus really hard to debug. I'm sure it can drive > people insane, > as they try to find out whether they've disabled

Re: [RFC PATCH v2 03/13] bootsplash: Flush framebuffer after drawing

Hi, > Actually, I don't want that :) > > This was a design decision that I've made to keep the code small and simple > to audit. > As it is, the simple bootsplash code will make 99% of people happy. You think only 1% of linux users have more than one monitor or a 4k screen? > I've made this

Re: [RFC PATCH v2 03/13] bootsplash: Flush framebuffer after drawing

Hi, > Actually, I don't want that :) > > This was a design decision that I've made to keep the code small and simple > to audit. > As it is, the simple bootsplash code will make 99% of people happy. You think only 1% of linux users have more than one monitor or a 4k screen? > I've made this

Re: [RFC PATCH v2 00/13] Kernel based bootsplash

Hi, > The problem that I am stumbling upon is different: > - the system starts with an FB driver > - after the ShowDelay time, Plymouth opens /dev/fb0 > - the system finally loads the DRM driver, which tries to kick the previous > FB driver > - loading the DRM driver fails because Plymouth

Re: [RFC PATCH v2 00/13] Kernel based bootsplash

Hi, > The problem that I am stumbling upon is different: > - the system starts with an FB driver > - after the ShowDelay time, Plymouth opens /dev/fb0 > - the system finally loads the DRM driver, which tries to kick the previous > FB driver > - loading the DRM driver fails because Plymouth

Re: [RFC PATCH v2 03/13] bootsplash: Flush framebuffer after drawing

Hi, On Tue, Dec 19, 2017 at 10:41 AM, Max Staudt wrote: > I'm hooking into the in-kernel terminal emulator, because the bootsplash is a > functional extension of that. It just happens that fbcon sits on top of FB, > so I > work with what I get. > > And the console in turn

Re: [RFC PATCH v2 03/13] bootsplash: Flush framebuffer after drawing

Hi, On Tue, Dec 19, 2017 at 10:41 AM, Max Staudt wrote: > I'm hooking into the in-kernel terminal emulator, because the bootsplash is a > functional extension of that. It just happens that fbcon sits on top of FB, > so I > work with what I get. > > And the console in turn happens to work on all

Re: [RFC PATCH v2 00/13] Kernel based bootsplash

Hi, > For example, having a userspace splash that starts as early as it can > (thus on vesafb/efifb on a PC) will cause the KMS driver to fail > reserving the entirety of video RAM, and thus fail loading. This cannot be > fixed. well the fix there is to use drm devices... like this:

Re: [RFC PATCH v2 00/13] Kernel based bootsplash

Hi, > For example, having a userspace splash that starts as early as it can > (thus on vesafb/efifb on a PC) will cause the KMS driver to fail > reserving the entirety of video RAM, and thus fail loading. This cannot be > fixed. well the fix there is to use drm devices... like this:

Re: [PATCH 3.13 35/99] tty: Set correct tty name in active sysfs attribute

Hi, On Sat, Feb 22, 2014 at 10:16 AM, Hannes Reinecke wrote: > And of course, checking for "!tty0" is the proper check for serial console. > Which, of course, means we have to stay with a broken kernel interface for > ever and ever. > > Innovation, here we come. So just so we're clear: 1) you

Re: [PATCH 3.13 35/99] tty: Set correct tty name in active sysfs attribute

Hi, On Sat, Feb 22, 2014 at 10:16 AM, Hannes Reinecke h...@suse.de wrote: And of course, checking for !tty0 is the proper check for serial console. Which, of course, means we have to stay with a broken kernel interface for ever and ever. Innovation, here we come. So just so we're clear: 1)

Re: [PATCH 3.13 35/99] tty: Set correct tty name in active sysfs attribute

Hi, (resending because my phone tried to send the reply as html mail and it got rejected) On Sat, Feb 22, 2014 at 9:27 AM, David Herrmann wrote: > > How about this: > > + driver = cs[i]->device(cs[i], ); > +/* special case for tty0 which must not be resolved */ > +

Re: [PATCH 3.13 35/99] tty: Set correct tty name in active sysfs attribute

Hi, (resending because my phone tried to send the reply as html mail and it got rejected) On Sat, Feb 22, 2014 at 9:27 AM, David Herrmann dh.herrm...@gmail.com wrote: How about this: + driver = cs[i]-device(cs[i], index); +/* special case for tty0 which must

Re: [PATCH 3.13 35/99] tty: Set correct tty name in active sysfs attribute

Hi, On Fri, Feb 21, 2014 at 11:01 AM, Kay Sievers wrote: > Why did the tty0 change to tty1 now? That doesn't look like a "driver > name" vs. "device name" issue? I don't know if it's intentional, but the patch does: + int index = cs[i]->index; ... + driver =

Re: [PATCH 3.13 35/99] tty: Set correct tty name in active sysfs attribute

Hi, On Fri, Feb 21, 2014 at 3:21 PM, Greg Kroah-Hartman wrote: > Ray, Josh, can I get some more information about this? Is this broken > in Linus's tree? Or did I get the backport wrong here? I don't think it's a problem with the backport specifically. To be honest, i'm not even 100% sure it

Re: [PATCH 3.11 085/121] tty: Set correct tty name in 'active' sysfs attribute

Hi, This broke plymouth, i think. Plymouth used the herustic: "/sys/class/tty/console/active contains something other than tty0" to mean "probably has serial consoles, force verbose messages instead of a splash screen". Now on a normal system it contains tty1. I pushed a commit to plymouth

Re: [PATCH 3.13 35/99] tty: Set correct tty name in active sysfs attribute

Hi, On Fri, Feb 21, 2014 at 3:21 PM, Greg Kroah-Hartman gre...@linuxfoundation.org wrote: Ray, Josh, can I get some more information about this? Is this broken in Linus's tree? Or did I get the backport wrong here? I don't think it's a problem with the backport specifically. To be honest, i'm

Re: [PATCH 3.13 35/99] tty: Set correct tty name in active sysfs attribute

Hi, On Fri, Feb 21, 2014 at 11:01 AM, Kay Sievers k...@vrfy.org wrote: Why did the tty0 change to tty1 now? That doesn't look like a driver name vs. device name issue? I don't know if it's intentional, but the patch does: + int index = cs[i]-index; ... + driver =

Re: [PATCH 3.11 085/121] tty: Set correct tty name in 'active' sysfs attribute

Hi, This broke plymouth, i think. Plymouth used the herustic: /sys/class/tty/console/active contains something other than tty0 to mean probably has serial consoles, force verbose messages instead of a splash screen. Now on a normal system it contains tty1. I pushed a commit to plymouth that

Re: freshmeat editorial on journaling filesystems

ut which should be eventually be supported by the kernel. I disagree. I think you should ask someone who works on more than one of the filesystems. That person will know the pros and cons of all of them, and surely will be objective. --Ray Strode - To unsubscribe from this list: send the line &qu

Re: freshmeat editorial on journaling filesystems

be eventually be supported by the kernel. I disagree. I think you should ask someone who works on more than one of the filesystems. That person will know the pros and cons of all of them, and surely will be objective. --Ray Strode - To unsubscribe from this list: send the line "unsubscribe linux-k

Re: Additional info. for PCI VIA IDE crazyness. Please read.

Is this problem possibly related to my issues on alpha? (when compiling for PC164 optimizations instead of generic alphaI get a lost interrupt message as well ) --Ray - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please

Re: Additional info. for PCI VIA IDE crazyness. Please read.

Is this problem possibly related to my issues on alpha? (when compiling for PC164 optimizations instead of generic alphaI get a lost interrupt message as well ) --Ray - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please

Re: Happy new year^H^H^H^Hkernel..

Eric W. Biederman writes, >Some arches have separate maintenance but I don't believe alpha is. >Though I do believe it has a separate mailing list for alpha specific things, >to get better signal to noise ratio. Great! Do you know where I can find more info about it? --Ray - To unsubscribe from

Happy new year^H^H^H^Hkernel..

>I want people to test it for a while, and I want to give other architectures >the chance to catch up with some of the changes Does that mean that other architectures have separate mailing lists and kernel source trees? Is that why i've been getting ignored =)? If so, what are they? I'd really

Happy new year^H^H^H^Hkernel..

I want people to test it for a while, and I want to give other architectures the chance to catch up with some of the changes Does that mean that other architectures have separate mailing lists and kernel source trees? Is that why i've been getting ignored =)? If so, what are they? I'd really

Re: Happy new year^H^H^H^Hkernel..

Eric W. Biederman writes, Some arches have separate maintenance but I don't believe alpha is. Though I do believe it has a separate mailing list for alpha specific things, to get better signal to noise ratio. Great! Do you know where I can find more info about it? --Ray - To unsubscribe from

Re: test13-pre7...

>The LDT fixes in particular fix some potentially random strange behaviour. >And the alpha memmove() thing was a showstopper bug on alphas. And the network lockup bug... --Ray - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL

Re: test13-pre7...

The LDT fixes in particular fix some potentially random strange behaviour. And the alpha memmove() thing was a showstopper bug on alphas. And the network lockup bug... --Ray - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED]

Re: [BUG] in 2.4.0test12 and earlier

o respond to my own mail, but does anyone here run linux on an Alpha? Is there a better place to ask these questions? --Ray Strode - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/

Re: Repeatable 2.4.0-test13-pre4 nfsd Oops rears it head again

> I don't want to have any more network card problems. > I'm tired of this crappy 8139. hmmm... The only cards I'll buy are 8139 based (SMC EZNet 10/100). They have worked great on every OS i've tried and only cost 14 bucks at my local CompUSA. I love em to pieces... The newer ones are only

Re: Repeatable 2.4.0-test13-pre4 nfsd Oops rears it head again

I don't want to have any more network card problems. I'm tired of this crappy 8139. hmmm... The only cards I'll buy are 8139 based (SMC EZNet 10/100). They have worked great on every OS i've tried and only cost 14 bucks at my local CompUSA. I love em to pieces... The newer ones are only like

Re: [BUG] in 2.4.0test12 and earlier

mail, but does anyone here run linux on an Alpha? Is there a better place to ask these questions? --Ray Strode - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/

[BUG] in 2.4.0test12 and earlier

it with several different NICs. Any ideas? Also, If I try to compile the kernel for PC164 instead of generic, then the computer gets irq probe errors for the hard drive, and the computer doesn't boot. Any ideas? I would really appreciate help in solving these problems. --Ray Strode

[BUG] in 2.4.0test12 and earlier

it with several different NICs. Any ideas? Also, If I try to compile the kernel for PC164 instead of generic, then the computer gets irq probe errors for the hard drive, and the computer doesn't boot. Any ideas? I would really appreciate help in solving these problems. --Ray Strode

hard lockups

) otherwise I get ide-probe errors on bootup. My network card is a 3com boomerang (I think? it uses 3c59x.o and it's PCI). Any ideas? --Ray Strode _ Get more from the Web. FREE MSN Explorer download : http