> Then HPA may ask: but why do you want to run the serial console at
> 115200?? The answer is simple: because we ...
... don't want to drag out debugging the kernel on a 38400 connection.
Because printks are our only debugging option ("thanks", Linus), and a slow
serial port block and can change
> IBM withdrew the proposal.
... from public view
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
I have a USB PCI card, which shows up as this in `lspci`:
00:09.0 USB Controller: VIA Technologies, Inc. VT82C586B USB (rev 04)
... it appears that they tossed the whole southbridge chip onto a pci
board, and disabled everything but USB. Anyway, this device seems to be
semi-functional under 2.2.
On 03 Mar 2001 12:54:36 +0100, Vojtech Pavlik wrote:
> No, they have a separate USB chip, but it has the same PCI ID as the
> builtin silicon in the southbridge.
Ah. I went and looked up that chip ID at via's website, and saw only
southbridge chips, no USB-only chips at all. But, my real questio
pyhsmem = `free | grep Mem | tr -s "/ / /" | cut -f2 -d" "`
On 03 Mar 2001 13:37:42 -0500, Denis Perchine wrote:
> Hello,
>
> actually the question is in subj.
> Problem is that there is a program which needs to know physical memory
> size. This information is used to justify memory consumption
physmem= `head -10 /var/log/dmesg | grep Memory: | cut -d" " -f2 | cut
-d "/" -f1 | cut -d"k" -f1`
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read
Now that 2.4 is out, it will probably be a few .x releases until 2.5
begins.
A discussion on Named Streams and Extended Attributes was put off until
2.5 earlier in the 2.4 development cycle. For compatibility with
existing, widely-deployed filesystems (e.g., NFS, XFS, BeFS, HFS, etc.),
Linux need
CORRECTION:
> existing, widely-deployed filesystems (e.g., NFS, XFS, BeFS, HFS, etc.),
NTFS---^
-
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
The man pages for open, read and write say that if a file is opened
using the O_NONBLOCK flag, then read() and write() will always return
immediately and not block the calling process. This does not appear to
be true; but perhaps I am doing something wrong. If I open() a file (on
2.2.18) from a fl
Alan Cox wrote:
>
> > using the O_NONBLOCK flag, then read() and write() will always return
> > immediately and not block the calling process. This does not appear to
> > be true; but perhaps I am doing something wrong. If I open() a file (on
> > 2.2.18) from a floppy or NFS mount (to test in a s
"James H. Cloos Jr." wrote:
>
> Michael> Please read and comment! :)
>
> There should be some discussion on what to do about filenames which
> contain colons in such a setup. Moving a file w/ a colon from a fs
> which does not support named streams to one which does should DTRT;
> exactly what
> What if you copy both 'filename' and 'filename:ext' onto the same fs?
> Do they get combined into one file?
ON Ext2, you get two files. On NTFS, you get one file, and a stream on that
file.
> Any semantics by which 'filename:stream' and 'filename' refer to the
> same file would be b0rken. If
Unfortunately, unix allows everything but "/" in filenames. This was
probably a mistake, as it makes it nearly impossible to augment the
namespace, but it is the reality.
Did you read the "new namespace" section of the paper?
It also talked a bit about supporting Extended Attributes, which are a
Robert Kaiser wrote:
>
> On Thu Jan 18 16:30:30 2001 [EMAIL PROTECTED] wrote
> > Has anyone had any luck getting a 2.4 kernel to run on Cobalt x86
> > hardware? It doesn't even seem to start (I get nothing on the screen from
> >t he kernel, it just sits there and does nothing). :(
>
> What proc
Mo McKinlay wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Today, Michael Rothwell ([EMAIL PROTECTED]) wrote:
>
> > Unfortunately, unix allows everything but "/" in filenames. This was
> > probably a mistake, as it makes it nearly i
Mo McKinlay wrote:
> openstream(file, stream, flags)
>
> Where 'file' should be an fd (although i'm sure the VFS gods will think of
> plenty of reasons why this is a bad idea, at which point I'll
> conventiently change my mind ;). Stream is simply the name of the stream,
> flags are as with open
Mo McKinlay wrote:
> (Take symbolic linking, for example - if you ln -s on VFAT, you get
> 'operation not permitted' - named stream/EA operations on a filesystem
> that doesn't support them should return the same, IMHO).
And they would, if the chosen namespace was not supported.
> Also, I don't
Mo McKinlay wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Today, Michael Rothwell ([EMAIL PROTECTED]) wrote:
>
> > The filesystem, when registering that it supports the "named streams"
> > namespace, could specify its preferred
Mo McKinlay wrote:
> Nono, that's not what I mean - each of the filesystems fails if it
> doesn't support what you're trying to do, that's given - but having a
> different delimeter registered by the filesystem (and hence the
> possibility of every single filesystem using a different delimeter) b
What version of the raidtools to I need for 2.2.18 software raid?
Documentation/md.txt has a non-functional URL in it.
Thanks.
-M
-
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
., Win32) apps, there are limitations on what a filename can
contain.
-M
- Original Message -
From: "Albert D. Cahalan" <[EMAIL PROTECTED]>
To: "Michael Rothwell" <[EMAIL PROTECTED]>
Cc: "Mo McKinlay" <[EMAIL PROTECTED]>; "Peter Samuelson&
GCCLOC=`which gcc`
rm `echo $GCCLOC`
ln -s `which kgcc` `echo $GCCLOC`
... repeat for g++
-M
Corisen wrote:
>
> thanks for the info. i've kgcc installed during RH7 installation. i've
> checked the version to be 2.91.66. i've used the following 2 methods with
> kgcc but it won't even allow me
One historically significant "Enterprise" OS is Multics. It had nine
major goals. Perhaps we should think about how Linux measures up to
these 1965 goals for "Enterprise Computing."
1) Convenient remote terminal use.
Telnet, ssh, X windows, rsh, vnc, "screen," ethernet, serial, etc. I
think we
Mike Dresser wrote:
> What's that $0.02 worth after 35 years of inflation?
About $6
-
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/
"Richard B. Johnson" wrote:
> Multics??? [..] way too many persons on this list who know the history of
> Unix to try this BS.
So, you're saying their nine goals were bullshit? Multics had a lot of
problems. But it did a lot of ground-breaking. Perhaps you should reply
to the nine goals, or the
Michael Rothwell wrote:
>
> Mike Dresser wrote:
>
> > What's that $0.02 worth after 35 years of inflation?
>
> About $6
Sorry.. six times a much... not six dollars. Which means $0.02 circa
1965 is 'worth' $0.12 today, given an average annual devaluation of
"Richard B. Johnson" wrote:
> Relating some "nine goals of 'Enterprise Computing'" to Multics is
> the bullshit.
Funny, I got those off the "Multics FAQ" page.
-M
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read
I'm looking for documentation on Ext2's support for sparse superblocks.
Canvasing search engines gets me the same two references to tune2fs and
the dac960. I've also looked in /usr/doc and
/usr/src/linux/Documentation without success.
What it the method uses to reduce the number of superblocks? H
Why is 2.2.18 proc_fs.c different than both 2.2.17 and 2.4.0? Cox, would
you accept a patch that makes 2.2.18 define create_proc_info_entry and
related functions the same way that 2.4.0 does?
2.2.17:
does not define this
2.2.18:
#define create_proc_info_entry(n, m, b, g) \
{ \
Is there a way to run NFS only on one NIC in a two-NIC box? I know
IPchains can be used to deny access from one card or another, but is
there a way to bind NFS specifically to one card and not the other?
-M
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a
Nathan Paul Simons wrote:
> kernel configs with the same kernel version. Since you will probably be
> changing the EXTRAVERSION variable anyway (to differentiate between different
How about addining an additional item to the config scripts: a "build
id". This can be any random string. It just ge
Attached.
diff -B --unidirectional-new-file --exclude-from=DiffExcludeList --recursive --unified
linux-2.2.16/include/asm-alpha/div64.h linux/include/asm-alpha/div64.h
--- linux-2.2.16/include/asm-alpha/div64.h Wed Dec 31 19:00:00 1969
+++ linux/include/asm-alpha/div64.h Fri Aug 11 20:0
I'm trying out the new VMWare for Linux, and noticed that if I let it
run for a couple of days, I get this:
Oct 16 15:07:49 cartman kernel: VM: do_try_to_free_pages failed for
kswapd...
... after which things go to hell pretty fast. The previous VMWare would
oops the kernel so badly that I would
I realize all of this is 2.5 material.
We had been talking about this earlier, until Viro and Cox told us to
quit until 2.5.
Alexander Viro wrote:
>
> It goes off-list.
But, in light of Andreas Gruenbacher's proposal
(http://lwn.net/2000/1026/a/extended-attributes.php3) and Stephen
Tweedie'
I saw that a number of people downloaded the document; did anyone read
it?
-M
Michael Rothwell wrote:
>
> I realize all of this is 2.5 material.
>
> We had been talking about this earlier, until Viro and Cox told us to
> quit until 2.5.
>
> Alexander Viro wrote:
>
I get a similar message with my 2.2.16 kernel:
Oct 23 15:02:12 cartman kernel: VM: do_try_to_free_pages failed for
kswapd...
Oct 23 15:02:12 cartman kernel: VM: do_try_to_free_pages failed for
klogd...
Oct 23 15:02:13 cartman kernel: VM: do_try_to_free_pages failed for
nmbd...
Oct 23 15:02:13
Is there a working userspace nfs v3 server for linux?
-M
-
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/
Andi Kleen wrote:
>
> On Wed, Nov 01, 2000 at 02:59:05PM -0500, Michael Rothwell wrote:
> > Is there a working userspace nfs v3 server for linux?
>
> Yes, just install user mode linux and use its v3 knfsd server.
Does anyone have any suggestions that aren't jokes, don
Aaron Denney wrote:
> I am not aware of any userspace NFSv3 server. Your best bet would
> probably to take the v2 server and mutate it. Why do you want this beast?
So I can use Linux rather than Solaris 7 and the Solstice Disk Suite,
which performs like crap thanks to UFS, and the Linux NFS v2
Okay, how about the nfsv3 kernel patch for 2.2.17? Does anyone know how
well (reliably) it works in client and server mode?
Thanks!
-M
-
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
Should kswapd and klogd ever get "do_try_to_free_pages failed"? when
this happens my machine is destabilized, and pauses briefly from time to
time before locking up or otherwise becoming inert. This is 2.2.16+USB.
Nov 7 14:51:36 cartman kernel: VM: do_try_to_free_pages failed for
kswapd...
Nov
64-bit printk.
-M
Alan Cox wrote:
>
> Ok last call for 2.2.18. The PS/2 cases I've looked at all appear to be
> ghost PS/2 interfaces created due to the USB support fooling programs.
diff -B --unidirectional-new-file --exclude-from=DiffExcludeList --recursive --unified
linux-2.2.16/include/as
Alan Cox wrote:
>
> > On Tue, Nov 07, 2000 at 09:02:36PM -0500, Michael Rothwell wrote:
> > > 64-bit printk.
> >
> > Please consider this one Alan, if not for v2.2.18, then at least for
> > v2.2.19pre1.
>
> Nobody has explained why we even need it.
Al
Linus Torvalds wrote:
>
> On Tue, 7 Nov 2000, Michael Rothwell wrote:
> >
> > Linus, can you post reasons why you keep ignoring^W rejecting the IrDA
> > patch?
>
> Basically, whatever Alan rants, I've not seen the patches all that many
> times at all.
>
Linus Torvalds wrote:
> and these people expect me to reply, sending long explanations of why I
> don't like them? After they did nothing of the sort for the code they
> claim should have been applied? Nada.
Did you say that to them? I'm not saying you're wrong; but did you tell
them that? It mig
Hello?
-M
Michael Rothwell wrote:
>
> Alan Cox wrote:
> >
> > > On Tue, Nov 07, 2000 at 09:02:36PM -0500, Michael Rothwell wrote:
> > > > 64-bit printk.
> > >
> > > Please consider this one Alan, if not for v2.2.18, then at least for
> >
Sounds great; unfortunately, the core group has spoken out against a
modular kernel.
Perhaps IBM should get together with SGI, HP and other interested
parties and start an Advanced Linux Kernel Project. Then they can run
off and make their scalable, modular, enterprise kernel and the Linus
Versio
Christoph Rohland wrote:
> If we would not allow binary only modules I would not have such a big
> problem with that...
I'm not sure how you would do that.
> I understand that the one size fits all approach has some limitations
> if you want to run on PDAs up to big iron. But a framework to ove
Christoph Rohland wrote:
> If we really need a special enterprise tree lets do
> it without module tricks.
Why? I think the IBM GKHI code would be of tremendous value. It would
make the kernel much more flexible, and for users, much more friendly.
No more patch-and-recompile to add a filesystem o
Lars Marowsky-Bree wrote:
> And we already refuse to support those kernels - your point being?
Who says you would support theirs? My point is, forks have been made in
the past and are useful for the people that use them, and prevent
"pollution" of the common kernel with hghly specialized modifica
Paul Jakma wrote:
>
> On Thu, 9 Nov 2000, Michael Rothwell wrote:
>
> > Why? I think the IBM GKHI code would be of tremendous value. It would
> > make the kernel much more flexible, and for users, much more friendly.
> > No more patch-and-recompile to add a filesys
Alexander Viro wrote:
>
> On Thu, 9 Nov 2000, Michael Rothwell wrote:
>
> > Same as before -- freedom and low cost. The primary advantae of Linux
> > over other OSes is the GPL.
>
> Now, that's more than slightly insulting...
Well, it wasn't meant to be. I
Alexander Viro wrote:
> > Figure 1?
>
> Use search engine. On google "See Figure 1" brings the thing in the first
> 5 hits.
http://www.google.com/search?q=See+Figure+1&btnG=Google+Search
->
http://spiffy.cso.uiuc.edu/~kline/Stuff/see-figure-1.html
->
http://spiffy.cso.uiuc.edu/~kline/Stuff/f-yo
Alan Cox wrote:
> RTLinux is hardly a fork. UcLinux is a fork, it has its own mailing list, web
> site and everything. Post 2.4 I'm still very interested in spending time merging
> the 2.4 uc and the main tree. I think it can be done and they are doing it in
> a way that leads logically to this.
Tim Waugh wrote:
> You forgot to 'cd .'
Look for "pebsak" messages in /var/log/syslog
;)
-
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/
Alexander "see figure 1" Viro wrote:
> Sorry. You don't "embed" the patch. You either get it accepted or not.
> Or you fork the tree and then it's officially None Of My Problems(tm).
Sounds like a good idea.
-M
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the bo
David Ford wrote:
> With kdb, after the panic happens, I can hit 'sr s' then 'g', it will
> OOPS (process sendmail) then continue. Without kdb, I am SOL and have
> to hit the power button. sysrq won't react.
Debugger good.
-
To unsubscribe from this list: send the line "unsubscribe linux-kerne
Matti Aarnio wrote:
> On Wed, Nov 08, 2000 at 04:35:33PM -0500, Michael Rothwell wrote:
> > Sounds great; unfortunately, the core group has spoken out against a
> > modular kernel.
>
> Really ?
>
> $ /sbin/lsmod
> Module Siz
Lars Marowsky-Bree wrote:
> And I am still very fond of the idea of crash dumping to a network server ;-)
I second that. Serial can be slow, and has that pesky cable-length
limit...
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTE
Where's the best place to get the latest 2.2.18 kernel? And does it
include the USB backport?
-
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/
t_intel.com503-677-5408|
> |NOTE: Any views presented here are mine alone|
> |& may not represent the views of my employer.|
> ---
>
> > From: Michael Rothwell [mailto:[EMAIL PROTECTED]]
> >
> > Where's the best
Alan Cox wrote:
>
> > Why is 2.2.18 proc_fs.c different than both 2.2.17 and 2.4.0? Cox, would
> > you accept a patch that makes 2.2.18 define create_proc_info_entry and
> > related functions the same way that 2.4.0 does?
>
> Send me a diff and I'll be happy to
Here it is, both inlined and as a
Michael Rothwell wrote:
>
> Alan Cox wrote:
> >
> > > Why is 2.2.18 proc_fs.c different than both 2.2.17 and 2.4.0? Cox, would
> > > you accept a patch that makes 2.2.18 define create_proc_info_entry and
> > > related functions the same way that 2.4.0 d
Alan Cox wrote:
>
> The patch I intend to be 2.2.18 is out as 2.2.18pre26 in the usual place.
> I'll move it over tomorrow if nobody reports any horrors, missing files etc
Fresh 2.2.17, "patch -p1 < /pre-patch-2.2.18-26"
can't find file to patch at input line 38909
Perhaps you used the wrong -
Ben Ford wrote:
> Why would you *ever* want to write a device driver in perl???
Well, Perl, I don't know. But the USB 'driver' for my Canon PowerShot
S20 runs in userspace. Seems a safer place to do things.
-M
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body
josef höök wrote:
>
> What about implementing 9P instead
That would rock. Plan9 is unix done the right way -- i.e., the fully
consistent way. I'd love to see 9p in Linux. We're heading that
direction anyway, with procfs, devfs, etc.
-
To unsubscribe from this list: send the line "unsubscribe li
Alan Cox wrote:
> Real bug - thanks. I'll squash that in 19pre1
When will you be starting 19pre1?
-
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/
Alexander Viro wrote:
> p9fs exists. I didn't see these patches since August, but probably I can poke
> Roman into porting it to the current tree. 9P is quite simple and unlike
> CORBA it had been designed for taking kernel stuff to userland. Besides,
> authors definitely understand UNIX...
I
> Also, 9P is a general communications framework only in the context of
> Plan9 itself. In reality it only applys directly/well to filesystem
> related issues... the reason it works well in Plan9 is that _everything_
> is a file (part of the beauty of plan9).
So... in a 9P-enabled system, you w
Alan Cox wrote:
> Ok this is the first block of changes before we merge the VM stuff. This is
> mostly the bits left over from the 2.2.18 port that were deferred as too
> risky near the end of a prerelease set and some bug swats
Here's the procfs patch again... :) Because the 2.2.18 procfs api i
Alan Cox wrote:
> Ok this is the first block of changes before we merge the VM stuff. This is
> mostly the bits left over from the 2.2.18 port that were deferred as too
> risky near the end of a prerelease set and some bug swats
And here is the 64-bit printk patch -- a backport of the 2.4.0 code
Heh. Mangleage. :)
Willy Tarreau wrote:
>
> Hello Michael, I wonder about this patch which only fixes an Id/author but no
> code. It may be perfectly normal, but could also come from a mangled file in
> one of your trees. Just for info anyway...
>
> Cheers,
> Willy
>
> > diff -r -u -x CVS -x
IPChains is essentially useless as a firewall due to its lack of
stateful packet filering. Will the IPTables code in 2.4 maintain
connection state?
-M
-
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 htt
"Michael H. Warfield" wrote:
> I think that's more than a little overstatement on your
> part. It depends entirely on the application you intend to put
> it to.
Fine. How do I make FTP work through it? How can I allow all outgoing
TCP connections without opening the network to inbound
"Michael H. Warfield" wrote:
> You can use spf to add some stateful inspection for PORT mode
> ftp. Personally, I like the masquerading option better, though.
Can you give an example of using MASQ selectively? I have real addresses
on both sides of the firewall, but want things like FTP
Alan Cox wrote:
> It does SYN checking. If you are running 'serious' security you wouldnt be
> allowing outgoing connections anyway. One windows christmascard.exe virus that
> connects back to an irc server to take input and you are hosed.
Thankfully, pine and mutt are, to date, immune to that k
Alan Cox wrote:
> There have been at least five holes found in pile that _could_ have been
> [speech]
> safe is the day you end up hurt.
Your specific example of an executable (windows) attachment, not buffer
overflows, etc. what what I was replying to. In general, you are
correct. Now, how abou
Felix von Leitner wrote:
>
> > IPChains is essentially useless as a firewall due to its lack of
> > stateful packet filering.
>
> Bullshit.
> Go back to the bowels or Redmond where you belong, luser.
Thanks. I appreciate that.
-M
-
To unsubscribe from this list: send the line "unsubscribe linu
Ruth Ivimey-Cook wrote:
> No. Java on NT uses proper NT threads. However, a thread on NT is a rather
> different beast to a cloned thread on Linux. I don't know whether the
> differences are important.
On Linux, threads are processes. On NT, processes are distinct from
threads, and usually have a
> On Wed, 3 Jan 2001, Dr. David Gilbert wrote:
>
> > I got wondering as to whether the various journaling file
> > system activities were designed to survive the occasional
> > unclean shutdown or were designed to allow the user to just pull
> > the plug as a regular means of shutting down.
>
How can I detect that open() has been called on a file in procfs that a
module provides? If I modprobe my module, open one or more if its proc
entries, then rmmod the module while the proc files are still open, then
the deletion of those entries is deferred. When I close the file(s), the
kernel oo
)
{
MOD_DEC_USE_COUNT;
return;
};
if (v==1)
{
MOD_INC_USE_COUNT;
return;
};
};
... right? :)
On 08 Mar 2001 11:01:28 -0500, Michael Rothwell wrote:
> How can I detect that open() has been called on a file in procfs that a
> module provides? If I modprobe my module, open one or more
Sweet! Thanks!
I'm working on 2.2 for now, but the 2.4 API looks nicer... :)
-M
On 08 Mar 2001 11:43:24 -0500, Alexander Viro wrote:
>
>
> On 8 Mar 2001, Michael Rothwell wrote:
>
> > Figured it out -- I think. This appears to be the answer:
> >
> &g
I'm installing Linux onto a Compaq iPaq IA-1 -- the little "MSN
Companion" thing. I wish Compaq didn't feel compelled to name everything
"iPaq." This device is essentially a laptop with a strange case, no hard
drive, and 32MB of RAM. It has a VIA chipset and four USB ports. The
southbridge is a VT
>From within a filesystem driver, how would I completely remove a page
cache mapping for an inode in 2.2.18?
-M
-
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/
Mo McKinlay wrote:
> I would too, but POSIX won't let us unless we start enforcing side-effect
> rules for all filesystems. Hence why I came up with openstream() :)
So, openstream() is probably the most painless way to get named streams
support into Linux in the immediate future. Openstream() wil
On 03 Feb 2001 14:22:02 -0600, Eric Sandeen wrote:
> The driver is included with the USB stuff for 2.2, but not in 2.4.
That's because we stopped fooling with 2.4 around the middle of the
pre-test-ac series of releases. We'll probably pick it back up around
2.4.7 or so.
> It also doesn't seem
Thanks. Has Brad Hards made his version available somewhere?
-M
- Original Message -
From: "Eric Sandeen" <[EMAIL PROTECTED]>
To: "Michael Rothwell" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Sunday, February 04, 2001 9:30 AM
Subject: R
rmat that
data and make it available via /proc, or something.
Does anyone have any suggestions before I go ugly-up the keyboard
driver?
Thanks,
--
Michael Rothwell
[EMAIL PROTECTED]
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMA
Input API looks nice. For now, I'll write a patch against pc_keyb.c to add a hook for
my qoder stuff, and a loadable module for the meat of the driver. Then I'll port up to
the input API. The Qoder is strictly ps/2 keyboard, as far as its interface goes, so I
cannot use the input API for now. I
Thanks, I'm loking through your driver now. Does the input api already/currently
support ps2 keyboards?
-M
On Sat, Jun 02, 2001 at 08:40:04PM -0700, James Simmons wrote:
>
> Hi!
>
>Your best bet for a kernel driver is to use the linux input api like
> the usb keyboard do. The drivers are
put api stuff for ps/2 devices will be a part of the
mainstream kernel...
--
Michael Rothwell
[EMAIL PROTECTED]
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
vger.kernel.org/majordomo-info.html
> > Please read the FAQ at http://www.tux.org/lkml/
>
> --
> ---
> Russell Leighton[EMAIL PROTECTED]
> ---
>
>
> -
> To unsub
On 19 Jun 2001 20:01:56 +0100, Alan Cox wrote:
> Linux inherits several unix properties which are not friendly to good state
> based programming - lack of good AIO for one.
Oh, how I would love for select() and poll() to work on files... or for
any other working AIO mothods to be present.
What
On 20 Jun 2001 10:14:48 +0100, Alan Cox wrote:
> It does.
... not
> They are always readable.
That's not very useful. Not in the sense of supporting aync,
non-blocking i/o to disk files without using threads.
--
Michael Rothwell
[EMAIL PROTECTED]
-
To unsubscribe from this lis
ctiva.com/
>
> Send all your spam to [EMAIL PROTECTED] (spam digging piggy)
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [EMAIL PROTECTED]
> More majordomo info at http://vger.kernel.org/majordomo-info
linux-kernel" in
> the body of a message to [EMAIL PROTECTED]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
Michael Rothwell
[EMAIL PROTECTED]
-
To unsubscribe from this list: send the line "unsubscribe lin
Add this:
append="mem=1024M"
to your lilo boot profiles.
... 2.4 correctly detects memory size more often than 2.2.16 ...
- Original Message -
From: "Edouard Soriano" <[EMAIL PROTECTED]>
Subject: 1GB system working with 64MB
> Hello Folks,
> Environment: linux 2.2.16smp
> RedHat 7.
Are there any negative effects of editing include/asm/param.h to change
HZ from 100 to 1024? Or any other number? This has been suggested as a
way to improve the responsiveness of the GUI on a Linux system. Does it
throw off anything else, like serial port timing, etc.?
-
To unsubscribe from t
Well, for kicks, I tried setting HZ to 1024 with 2.2.19. It seemed a
little more responsive, but that could be psychosomatic. :) I did notice
that I was unable to sync my palm pilot until I set it back to 100.
YMMV. The most useful "performace" tweak for a GUI that I've come across is:
#define
1 - 100 of 107 matches
Mail list logo
