On Thu, 28 Jun 2001, Laramie Leavitt wrote:
> > dmesg buffer space is rather limited and IMHO there isn't space to
> > waste on credit-giving in boot logs.
>
> Here here. You don't see annoying log-eating copyright messages
> printed out in the Windows boot. Just imagine:
There's a difference;
On Thu, 28 Jun 2001, Laramie Leavitt wrote:
dmesg buffer space is rather limited and IMHO there isn't space to
waste on credit-giving in boot logs.
Here here. You don't see annoying log-eating copyright messages
printed out in the Windows boot. Just imagine:
There's a difference;
Just for the record, the via-rhine.c in 2.4.5 still does not work if you
soft-boot the computer (at least one a machine here), MAC address shows up
as 00:00:00:00:00:00 and it fails - but a cold boot (power cable off, no
standby power) makes it work.
I read something that we'd need to reload the
Can someone elaborate on why it's bad to refer to tsk directly below (this
is a 2.4.5 change in x86) and why it's needed on x86 and not other archs..
What should I do for an arch that does not have a "cr3" machine register
to check with ?
/BW
vmalloc_fault:
{
/*
On Mon, 4 Jun 2001 [EMAIL PROTECTED] wrote:
> I don't know the details of the implementation, but the CRIS port
> (ETRAX 100LX) has support for USB but no PCI.
A builtin non-PCI USB-host controller, that is. And the driver is in the
kernel so we do support it as well :)
/BW
> > > AC> o
On Tue, 5 Jun 2001, David Woodhouse wrote:
> The flash mapping driver arch/cris/drivers/axisflashmap.c uses a cached
> mapping of the flash chips for bulk reads, but obviously an uncached mapping
> for sending commands and reading status when we're actually writing to or
> erasing parts of the
On Tue, 5 Jun 2001, David Woodhouse wrote:
The flash mapping driver arch/cris/drivers/axisflashmap.c uses a cached
mapping of the flash chips for bulk reads, but obviously an uncached mapping
for sending commands and reading status when we're actually writing to or
erasing parts of the chip.
On Mon, 4 Jun 2001 [EMAIL PROTECTED] wrote:
I don't know the details of the implementation, but the CRIS port
(ETRAX 100LX) has support for USB but no PCI.
A builtin non-PCI USB-host controller, that is. And the driver is in the
kernel so we do support it as well :)
/BW
AC o Make
Can someone elaborate on why it's bad to refer to tsk directly below (this
is a 2.4.5 change in x86) and why it's needed on x86 and not other archs..
What should I do for an arch that does not have a cr3 machine register
to check with ?
/BW
vmalloc_fault:
{
/*
While we're on cosmetics... how about imprisonment for the person who
chose yellow on light grey for the first letters in each option...
/Bjorn
On Thu, 17 May 2001, Martin.Knoblauch wrote:
> this is most likely just a small issue. If I knew where to look, I
> would try to fix it and submit a
While we're on cosmetics... how about imprisonment for the person who
chose yellow on light grey for the first letters in each option...
/Bjorn
On Thu, 17 May 2001, Martin.Knoblauch wrote:
this is most likely just a small issue. If I knew where to look, I
would try to fix it and submit a
On Mon, 7 May 2001, Richard B. Johnson wrote:
> Basically, "no copy" is an academic exercise. It makes the first
> packet get sent more quickly, after which everything slows to
> the natural bandwidth of the system.
>
> If you used a server for multicast-only. In other words, you
> just spewed
On Mon, 7 May 2001, Richard B. Johnson wrote:
Basically, no copy is an academic exercise. It makes the first
packet get sent more quickly, after which everything slows to
the natural bandwidth of the system.
If you used a server for multicast-only. In other words, you
just spewed out
On Wed, 2 May 2001, Terry Barnaby wrote:
> However, I note that if the user just mallocs memory and does not access
> it
> (No physical memory pages created) and then passes this virtual address
> space
> to the driver which performs a map_user_kiobuf() on it, the resulting
> kiobuf
> structure
On Wed, 2 May 2001, Terry Barnaby wrote:
However, I note that if the user just mallocs memory and does not access
it
(No physical memory pages created) and then passes this virtual address
space
to the driver which performs a map_user_kiobuf() on it, the resulting
kiobuf
structure has all
On Fri, 27 Apr 2001, Padraig Brady wrote:
> for a partition. If I understand correctly ramfs just points
> to the file data which are pages in the cache marked not to be
It does not even do that - as of 2.4, the VFS in the kernel also knows how
to cache a filestructure itself. It's in the
On Fri, 27 Apr 2001, Padraig Brady wrote:
for a partition. If I understand correctly ramfs just points
to the file data which are pages in the cache marked not to be
It does not even do that - as of 2.4, the VFS in the kernel also knows how
to cache a filestructure itself. It's in the
On Thu, 26 Apr 2001, Padraig Brady wrote:
> I'm working on an embedded system here which has no harddisk.
> So, I can't swap to disk and need to have /var & /tmp in RAM.
> I'm confused between the various options for in RAM file-
> systems. At the moment I've created a ramdisk and made an
> ext2
On Thu, 26 Apr 2001, Padraig Brady wrote:
I'm working on an embedded system here which has no harddisk.
So, I can't swap to disk and need to have /var /tmp in RAM.
I'm confused between the various options for in RAM file-
systems. At the moment I've created a ramdisk and made an
ext2
Hi!
Problem description:
* drivers/ide/ide.c assumes the IDE controller is mapped in such a way
that it can access it by "hardcoded" I/O commands (IN_BYTE/OUT_BYTE)
* drivers/ide/ide.c assumes that polled ide/atapi transfers should be
done the way a PC would
*
A similar phenomenon happens when you simply copy a file - file A is read
into the cache and file B is written to the cache, until the memory runs
out. Then both start to flush at the same time, creating a horrible
performance hit (especially if A and B are on the same disk :)
I don't know a
A similar phenomenon happens when you simply copy a file - file A is read
into the cache and file B is written to the cache, until the memory runs
out. Then both start to flush at the same time, creating a horrible
performance hit (especially if A and B are on the same disk :)
I don't know a
Hi,
regarding drivers/parport/*
is there any particular reason as to why the different parport drivers
aren't initialized using module_init() ? Like weird init order
dependencies and stuff.
Looking at parport_init itself (which has hardcoded init calls to the
different drivers right now) it
Hi,
regarding drivers/parport/*
is there any particular reason as to why the different parport drivers
aren't initialized using module_init() ? Like weird init order
dependencies and stuff.
Looking at parport_init itself (which has hardcoded init calls to the
different drivers right now) it
On Thu, 5 Apr 2001, Jani Monoses wrote:
> although the comments in errno.h say that ERESTARTSYS should not be seen
> by userland,many drivers seam to return it from their
> file_operations.Should glibc convert this errno so that the user program
> sees something meaningful?Because it does not.Is
On Thu, 5 Apr 2001, Jani Monoses wrote:
although the comments in errno.h say that ERESTARTSYS should not be seen
by userland,many drivers seam to return it from their
file_operations.Should glibc convert this errno so that the user program
sees something meaningful?Because it does not.Is
On 4 Apr 2001, Andi Kleen wrote:
> > >> Hello, I would like to know why you put this two functions:
> > >> void scheduling_functions_start_here(void) { }
> > >> ...
> > >> void scheduling_functions_end_here(void) { }
> This is needed for a very bad hack to get the EIP information in ps -lax:
On 4 Apr 2001, Andi Kleen wrote:
Hello, I would like to know why you put this two functions:
void scheduling_functions_start_here(void) { }
...
void scheduling_functions_end_here(void) { }
This is needed for a very bad hack to get the EIP information in ps -lax:
most programs
On Mon, 26 Mar 2001, Eric S. Raymond wrote:
> (2) Fix up 20 cris-architecture configuration symbols lacking a CONFIG_
> prefix, so they obey CML1/CML2 conventions and can be detected by
> `make dep', also static-analysis tools and consistency checkers.
> This is a BUG FIX in CML1.
No
On Mon, 26 Mar 2001, Eric S. Raymond wrote:
(2) Fix up 20 cris-architecture configuration symbols lacking a CONFIG_
prefix, so they obey CML1/CML2 conventions and can be detected by
`make dep', also static-analysis tools and consistency checkers.
This is a BUG FIX in CML1.
No
On Fri, 23 Mar 2001, David Woodhouse wrote:
> > 1. RAMFS is just more stable in terms of less complexity, less bugs reported
> > over the time, etc.
> > 2. RAMFS is a fairly robust filesystem and all features required as far as I can
> > tell.
Ok, ramfs is really simple, but heck, cramfs is
On Fri, 23 Mar 2001, David Woodhouse wrote:
1. RAMFS is just more stable in terms of less complexity, less bugs reported
over the time, etc.
2. RAMFS is a fairly robust filesystem and all features required as far as I can
tell.
Ok, ramfs is really simple, but heck, cramfs is not much
On Sat, 20 Jan 2001, Martin MaD Douda wrote:
> On Fri, 19 Jan 2001, Michael Lindner wrote:
> > data is generated as a result of data received via a select(),
> > the next delivery occurs a clock tick later, with the machine
> > mostly idle.
>
> The machine is in fact not idle - there is a task
On Sat, 20 Jan 2001, Martin MaD Douda wrote:
On Fri, 19 Jan 2001, Michael Lindner wrote:
data is generated as a result of data received via a select(),
the next delivery occurs a clock tick later, with the machine
mostly idle.
The machine is in fact not idle - there is a task running -
On Mon, 8 Jan 2001, Linus Torvalds wrote:
> Please show them, anyway. What does "ls -ld / /etc /etc/passwd" say?
Heh... /etc and /etc/passwd were allright... but / was fscked (or not,
maybe :)
drwx- 500 0 both locked from other users and 500 as owner..
> 99% says that one of the
On Mon, 8 Jan 2001, Linus Torvalds wrote:
Please show them, anyway. What does "ls -ld / /etc /etc/passwd" say?
Heh... /etc and /etc/passwd were allright... but / was fscked (or not,
maybe :)
drwx- 500 0 both locked from other users and 500 as owner..
99% says that one of the
Ok.. I'm going bananas. It could be a 4am braindeath or a rh7.0 bungholio
but this is annoying:
main(int argc, char **argv)
{
int fd;
setfsuid(atoi(argv[1]));
fd = open("/etc/passwd", O_RDONLY);
printf("got fd %d\n", fd);
}
[root@wizball /root]# ./setfstest 0
Ok.. I'm going bananas. It could be a 4am braindeath or a rh7.0 bungholio
but this is annoying:
main(int argc, char **argv)
{
int fd;
setfsuid(atoi(argv[1]));
fd = open("/etc/passwd", O_RDONLY);
printf("got fd %d\n", fd);
}
[root@wizball /root]# ./setfstest 0
with initialization calls.
-BW
> On Tue, 28 Nov 2000, Bjorn Wesen wrote:
> > Hi! Quick question: is it possible to write an IDE driver for a controller
> > that is not mappable using outp and those memory-mapped thingys ?
> >
> > I see all the nice overridea
ation calls.
-BW
On Tue, 28 Nov 2000, Bjorn Wesen wrote:
Hi! Quick question: is it possible to write an IDE driver for a controller
that is not mappable using outp and those memory-mapped thingys ?
I see all the nice overrideables in struct hwif_s but the main code still
uses OUT_BYTE w
On Thu, 23 Nov 2000, Andreas Bombe wrote:
> > I may be wrong on this, but I thought that copy_{to,from}_user are
> > only necessary if the address range you are accessing might cause a
> > fault which Linux cannot handle (ie. one which would cause the
> > application to segfault if it accessed
On Wed, 27 Sep 2000, Hen, Shmulik wrote:
> Is there a good source of information that describes the changes in network
> driver interface between 2.2.x and 2.4.x kernels ?
Try a diff -u of skeleton.c in the both kernels. If the skeleton driver is
correct that is :)
It didn't look very
42 matches
Mail list logo
