* NFS as a Cluster File System.
From: Lorn Kay @ 2003-01-09 19:39 UTC (permalink / raw)
To: nfs, linux-ha
Is NFS a viable CFS? (I'm cross posting this due to a discussion on the the
linux-ha list recently.)
NFS has a bad reputation probably due to (at least) the following:
It has been used in networking environments where different server hardware
configurations (NICS, drivers, etc.) running different operating systems
have connected to each other (in many-to-many configurations).
It “grew up” on networks that were perhaps unstable, or immature
(“Someone’s kicked the token ring coax cable laying on the floor again”)
long before switches were common place, and the network was loaded down with
all kinds of network traffic.
It wasn’t understood very well. Since the default mount options worked,
system administrators often didn’t fully understand the ramifications of
their NFS client mount option choices.
It relied on UDP, which is susceptible to huge retransmission efforts on
noisy or lossy networks.
NFS was used over many-hop WAN connections.
NFS servers were often used for many other tasks, not just NFS.
A cluster configuration, however, offers several advantages over the typical
NFS configuration:
All NFS clients (the cluster nodes) run the same operating system (Linux).
All clients run the same version of NFS and the kernel.
All clients use the same network tuned configuration.
A physical network can be dedicated to NFS. (Using a high quality switch,
with short data-center-only cable runs.)
All clients connect to one NFS server.
The NFS server is a high-quality dedicated machine (Net App, EMC, etc.)
Only one mount point need be used with one set of mount options.
Linux clients can use TCP instead of UDP.
Except for the vagaries of the load placed on the cluster nodes, this sounds
like a test lab environment. If NFS can’t work in this environment where
will it ever work?
--K
_________________________________________________________________
STOP MORE SPAM with the new MSN 8 and get 2 months FREE*
http://join.msn.com/?page=features/junkmail
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
^ permalink raw reply
* Re: rotation.
From: James Simmons @ 2003-01-09 19:44 UTC (permalink / raw)
To: Geert Uytterhoeven
Cc: Linux Fbdev development list, Linux Kernel Mailing List
In-Reply-To: <Pine.GSO.4.21.0301081120540.21171-100000@vervain.sonytel.be>
> Where are you going to implement the rotation? At the fbcon or fbdev level?
We already have a hook for hardware acceleration in struct fb_ops.
> Fbcon has the advantage that it'll work for all frame buffer devices.
The fbdev level will have the functionalty but fbcon is the one that needs
it.
^ permalink raw reply
* Rage1128
From: Jon Smirl @ 2003-01-09 19:34 UTC (permalink / raw)
To: fbdev
Does anyone on this list have a Rage128 manual?
Can anyone point me to source code for directly
reseting a Rage128? I already have the emulate real
mode and call C000:3 method.
=====
Jon Smirl
jonsmirl@yahoo.com
__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
^ permalink raw reply
* PMS messaging program: where?
From: Tim Neu @ 2003-01-09 19:33 UTC (permalink / raw)
To: linux-hams
In-Reply-To: <Pine.LNX.4.44.0301091159220.1414-100000@oh2bns.ampr.org>
The linux ax25 faq refers to a packet radio mail program called "pms". I
can't seem to find this program anywhere! I installed the debian package by
the same name - but that doesn't seem to be anything related to packet radio.
(It's some sort of python library)
I am all googled out. I suppose if it were so easy to find, the URL would be
in the FAQ. That or I am just having no luck whatsoever.
Does this program still exist, or is it superceeded by something else?
Thanks in advance.
-Tim
KC0LQL
--
Open WebMail Project (http://openwebmail.org)
Debian Project (http://www.debian.org)
^ permalink raw reply
* Re: "Mother" == "computer-illiterate"
From: Val Henson @ 2003-01-09 19:40 UTC (permalink / raw)
To: linux-kernel; +Cc: David van Hoose, dpaun, rms, Miles Bader, lm, acahalan
In-Reply-To: <20030109072043.GE26010@boardwalk>
On Thu, Jan 09, 2003 at 12:20:43AM -0700, Val Henson wrote:
> On Wed, Jan 08, 2003 at 11:29:47AM +0900, Miles Bader wrote:
> >
> > If someone's mom (having heard the gossip) asks their computer-literate
> > child, `What is this XXX thing, anyway?', the answer is likely to be
> > very different when XXX is "GNU" as opposed to when XXX is "Linux".
>
> How come no one ever talks about a Linux distribution so easy that
> your grandfather could install it? Or a kernel configuration tool so
> simple that even Uncle Timmy can use it?
>
> Can we quit with the "clueless mother" examples already? My own
> mother has installed more distributions of Linux than I've even logged
> into. I know quite a few mothers who have PhDs in CS, own several
> CS-related patents, and/or made important fundamental discoveries in
> CS. Hint: Find out who invented the spanning tree algorithm for
> ethernet bridges, $10 ThinkGeek gift certificate to the first person
> who emails me the correct answer.
And the winner is David Hoose, who sent the answer to me 10 minutes
after the message to linux-kernel arrived in my mail queue. The
answer is:
Radia Perlman
She is the inventor of the spanning tree algorithm, the author of
"Interconnections: Bridges, Routers, Switches, and Internetworking
Protocols" from Addison-Wesley, and the mother of at least two
children. Honorable mention to: Joe Perches, Joe Sloan, Chris Ricker,
Larry McVoy, and "Disconnect," real name withheld.
-VAL
P.S. For extra credit (but no ThinkGeek certificate) you can look up
the following women in computer science, some of whom are mothers:
Mary Baker, Margo Seltzer, Monica Lam, Ellen Spertus, Carla Ellis, and
Barbara Simons.
^ permalink raw reply
* Re: [PATCH] PATCH: IPMI driver
From: Dave Jones @ 2003-01-09 19:37 UTC (permalink / raw)
To: Alan Cox; +Cc: Corey Minyard, Linux Kernel Mailing List
In-Reply-To: <1042143476.27796.66.camel@irongate.swansea.linux.org.uk>
On Thu, Jan 09, 2003 at 08:17:57PM +0000, Alan Cox wrote:
> On Thu, 2003-01-09 at 19:20, Dave Jones wrote:
> > time_diff = ((jiffies_now - kcs_info->last_timeout_jiffies)
>
> Thats valid for unsigned maths
> 0x00000001 - 0xFFFFFFFF = 0x00000002
Doh, I've made this mistake before.. Thanks for clarifying.
Dave
--
| Dave Jones. http://www.codemonkey.org.uk
^ permalink raw reply
* Re: [PATCH] PATCH: IPMI driver
From: Corey Minyard @ 2003-01-09 19:37 UTC (permalink / raw)
To: Dave Jones; +Cc: Alan Cox, Linux Kernel Mailing List
In-Reply-To: <20030109192022.GA5693@codemonkey.org.uk>
Dave Jones wrote:
>On Thu, Jan 09, 2003 at 01:16:29PM -0600, Corey Minyard wrote:
>
> > >Pull the 2.5 port from openipmi.sourceforge.net saves you doing the port
> > >yourself.
> > >
> > Definately pull the 2.5 port from there, as there are some differences
> > between the 2.4 and 2.5 versions.
>
>I had a quick skim through the patch.
>Is the handling of jiffies wraps done correctly ? It doesn't
>look like it...
>
>time_diff = ((jiffies_now - kcs_info->last_timeout_jiffies)
>
> Dave
>
I don't understand why that wouldn't work. Those are both unsigned long
values. Assuming twos complement, the time difference could be correct,
even in a wraparound case (unless a very large number of jiffies has
transpired, but that will never be the case here).
Am I missing something here?
-Corey
^ permalink raw reply
* Re: Wireless Extensions v16-3 - clean patches
From: Joshua M. Kwan @ 2003-01-09 19:33 UTC (permalink / raw)
To: jt; +Cc: linux-kernel
In-Reply-To: <20030109181340.GB24023@bougret.hpl.hp.com>
[-- Attachment #1: Type: text/plain, Size: 3071 bytes --]
Hi Jean,
> For 2.5.X : my Pcmcia cards still don't work with 2.5.54, so
> I'm currently no too worried about 2.5.X at the moment.
They didn't work for me either. But I read an old LKML post from about
3 months ago which said that since 16-bit PCMCIA cards are ISA based
one must enable CONFIG_ISA to get those sort of cards working, so I
did that and now everything is working just fine.
It's weird because i thought the WaveLAN/IEEE was a 32-bit CardBus
device.
> Also, the current WE16-3 may not be the final version, as I'm
> waiting for feedback from driver authors. Talking of feedback, which
> part of WE16 do you need and why ?
I like the enhanced iwspy support. It is currently working just fine for
me! Basically, it allows me to check on my server whether any vagabonds
are camping on my AP (running hostap), and if my dad says 'the internet
stopped working' i can see whether his wifi card crapped out. I don't
quite remember now but I recall having some problems with earlier WE
and hostap_pci using iwspy. It might not have been the fault of WE but
of some other factors with my hostap build, and in troubleshooting I
upgraded to WE16 to see whether it was the problem.
Another reason is 'just for the hell of it.' :)
Regards
Josh
On Thu, Jan 09, 2003 at 10:13:41AM -0800, Jean Tourrilhes wrote:
> On Wed, Jan 08, 2003 at 08:31:19PM -0800, Joshua M. Kwan wrote:
> > Hi Jean,
> >
> > I have attached two patches that allow current 2.5.54 BK and 2.4.20
> > vanilla to patch cleanly from whatever WE they came with to WE16,
> > from your site. This is easier since the patches on your website for
> > 2.4.20 require two patches, and the 2.5.x one has a single reject
> > that was not hard to resolve (just a few line breaks here and there
> > and editing of the surrounding text confused patch.)
> >
> > For 2.5, the BK i diffed against was a fresh tree from today, but
> > since you're the one that makes all the changes to those files
> > anyway, it really doesn't matter until a new WE is pushed! And then
> > this patch won't be necessary at all :)
> >
> > Both patches should be placed in the root of the source tree and
> > applied with -p0.
> >
> > Hope this can benefit others who would like to easily upgrade their
> > WE :)
> >
> > Regards
> > Josh
>
> Thanks for the good work !
>
> For 2.4.X : 2.4.21-pre2 has WE-15, so if you get it it's only
> one patch (the one on my page).
> For 2.5.X : my Pcmcia cards still don't work with 2.5.54, so
> I'm currently no too worried about 2.5.X at the moment.
> Also, the current WE16-3 may not be the final version, as I'm
> waiting for feedback from driver authors. Talking of feedback, which
> part of WE16 do you need and why ?
>
> Have fun...
>
> Jean
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
^ permalink raw reply
* [PATCH] module-init-tools update
From: carbonated beverage @ 2003-01-09 19:27 UTC (permalink / raw)
To: torvalds; +Cc: linux-kernel
Hi Linus,
Here's a small patch for Documentation/Changes and scripts/ver_linux
to use depmod instead of rmmod as per Rusty's suggestion.
rmmod will exec the old version of the modutils depending on the
command-line, whereas depmod will give its own version instead.
Please apply.
-- DN
Daniel
--- Documentation/Changes.old Thu Jan 9 10:51:36 2003
+++ Documentation/Changes Thu Jan 9 11:27:54 2003
@@ -52,7 +52,7 @@
o Gnu make 3.78 # make --version
o binutils 2.9.5.0.25 # ld -v
o util-linux 2.10o # fdformat --version
-o module-init-tools 0.9 # rmmod -V
+o module-init-tools 0.9 # depmod -V
o e2fsprogs 1.29 # tune2fs
o jfsutils 1.0.14 # fsck.jfs -V
o reiserfsprogs 3.6.3 # reiserfsck -V 2>&1|grep reiserfsprogs
--- scripts/ver_linux.old Thu Jan 9 10:52:10 2003
+++ scripts/ver_linux Thu Jan 9 11:27:57 2003
@@ -28,7 +28,7 @@
mount --version | awk -F\- '{print "mount ", $NF}'
-rmmod -V 2>&1 | awk 'NR==1 {print "module-init-tools ",$NF}'
+depmod -V 2>&1 | awk 'NR==1 {print "module-init-tools ",$NF}'
tune2fs 2>&1 | grep "^tune2fs" | sed 's/,//' | awk \
'NR==1 {print "e2fsprogs ", $2}'
^ permalink raw reply
* Re: [PATCH] PATCH: IPMI driver
From: Alan Cox @ 2003-01-09 20:17 UTC (permalink / raw)
To: Dave Jones; +Cc: Corey Minyard, Linux Kernel Mailing List
In-Reply-To: <20030109192022.GA5693@codemonkey.org.uk>
On Thu, 2003-01-09 at 19:20, Dave Jones wrote:
> time_diff = ((jiffies_now - kcs_info->last_timeout_jiffies)
Thats valid for unsigned maths
0x00000001 - 0xFFFFFFFF = 0x00000002
Alan
^ permalink raw reply
* Re: Calling Application
From: Der Herr Hofrat @ 2003-01-09 19:21 UTC (permalink / raw)
To: Aman; +Cc: linuxppc embedded
In-Reply-To: <001b01c2b810$7ec76720$370da8c0@aman>
>
> Hi All
>
> This might be a basic question. I have build the linux kernel for custom
> board which has PPC 440GP as its processor. I have also build my
> application. Now I wanted to call my application after the kernel boots up.
> Can you tell me where I hv to call my application.
>
pass the kernel a init=/bin/my_app at the boot-prompt if you realy want only
that one app to run, otherwise use the inittab or one of the resource scripts
in /etc/rc.d to launch your application.
hofrat
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply
* Re: MB without keyboard controller / USB-only keyboard ?
From: Alan Cox @ 2003-01-09 20:13 UTC (permalink / raw)
To: Pete Zaitcev; +Cc: Linux Kernel Mailing List
In-Reply-To: <200301091916.h09JGI228106@devserv.devel.redhat.com>
On Thu, 2003-01-09 at 19:16, Pete Zaitcev wrote:
> I fail to see the point, Alan. Stephan's BIOS does exactly the
> right thing: it emulates BIOS INTs which allow to read buffered
> keystrokes, but it does not do SMM tricks to emulate port 0x60.
> This is great, now pc_keyb.d must do detection right. It must
> not loop endlessly if 0xff is returned from inb(). It's a bug.
Thats what I wanted to verify.
^ permalink raw reply
* Re: [PATCH] PATCH: IPMI driver
From: Dave Jones @ 2003-01-09 19:20 UTC (permalink / raw)
To: Corey Minyard; +Cc: Alan Cox, Linux Kernel Mailing List
In-Reply-To: <3E1DCA8D.4040005@acm.org>
On Thu, Jan 09, 2003 at 01:16:29PM -0600, Corey Minyard wrote:
> >Pull the 2.5 port from openipmi.sourceforge.net saves you doing the port
> >yourself.
> >
> Definately pull the 2.5 port from there, as there are some differences
> between the 2.4 and 2.5 versions.
I had a quick skim through the patch.
Is the handling of jiffies wraps done correctly ? It doesn't
look like it...
time_diff = ((jiffies_now - kcs_info->last_timeout_jiffies)
Dave
--
| Dave Jones. http://www.codemonkey.org.uk
^ permalink raw reply
* Re: Calling Application
From: Dr. Craig Hollabaugh @ 2003-01-09 19:12 UTC (permalink / raw)
To: Aman, linuxppc embedded
In-Reply-To: <001b01c2b810$7ec76720$370da8c0@aman>
At 12:24 AM 1/10/2003 +0530, Aman wrote:
>
>Hi All
>
>This might be a basic question. I have build the linux kernel for custom
>board which has PPC 440GP as its processor. I have also build my
>application. Now I wanted to call my application after the kernel boots up.
>Can you tell me where I hv to call my application.
look at /etc/inittab, put your application in one of those scripts or call it directly from the within the inittab, much like the gettys.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply
* [BK PATCH] USB changes for 2.5.55
From: Greg KH @ 2003-01-09 19:17 UTC (permalink / raw)
To: Linus Torvalds; +Cc: Kernel Mailing List, linux-usb-devel
In-Reply-To: <Pine.LNX.4.44.0301082033410.1438-100000@penguin.transmeta.com>
On Wed, Jan 08, 2003 at 08:35:45PM -0800, Linus Torvalds wrote:
>
> All over the map again: arm, alpha, ppc, sparc, usb, isdn, dm, sysfs,
> knfsd - you name it.
Hm, looks like you didn't get the USB changes I sent :)
Here they are again, updated for your latest tree:
Please pull from: bk://linuxusb.bkbits.net/linus-2.5
thanks,
greg k-h
Documentation/usb/scanner-hp-sane.txt | 79 --------
Documentation/usb/scanner.txt | 329 +++++++++++++---------------------
drivers/usb/class/usblp.c | 3
drivers/usb/core/hcd-pci.c | 16 -
drivers/usb/core/hcd.c | 34 +--
drivers/usb/core/hub.c | 70 +++----
drivers/usb/core/usb-debug.c | 2
drivers/usb/core/usb.c | 38 +--
drivers/usb/host/ehci-dbg.c | 40 ----
drivers/usb/host/ehci-hcd.c | 11 -
drivers/usb/host/ehci-q.c | 19 +
drivers/usb/host/ehci.h | 2
drivers/usb/host/ohci-dbg.c | 35 ++-
drivers/usb/host/ohci-hcd.c | 10 -
drivers/usb/host/ohci-hub.c | 2
drivers/usb/host/ohci-mem.c | 2
drivers/usb/host/ohci-q.c | 4
drivers/usb/image/Kconfig | 4
drivers/usb/image/mdc800.c | 4
drivers/usb/image/scanner.c | 203 +++++++-------------
drivers/usb/image/scanner.h | 24 --
drivers/usb/input/pid.c | 45 +---
drivers/usb/misc/Makefile | 6
drivers/usb/misc/atmsar.c | 177 +++++++-----------
drivers/usb/misc/atmsar.h | 27 +-
drivers/usb/misc/auerswald.c | 7
drivers/usb/misc/brlvger.c | 21 --
drivers/usb/misc/rio500.c | 5
drivers/usb/misc/speedtouch.c | 80 ++++----
drivers/usb/misc/usbtest.c | 306 +++++++++++++++++++++++++++++++
drivers/usb/net/kaweth.c | 8
drivers/usb/net/pegasus.c | 5
drivers/usb/net/pegasus.h | 4
drivers/usb/net/rtl8150.c | 5
drivers/usb/net/usbnet.c | 22 ++
drivers/usb/serial/bus.c | 9
drivers/usb/serial/empeg.c | 12 -
drivers/usb/serial/ezusb.c | 4
drivers/usb/serial/generic.c | 6
drivers/usb/serial/io_edgeport.c | 38 +--
drivers/usb/serial/io_ti.c | 58 ++---
drivers/usb/serial/ir-usb.c | 16 -
drivers/usb/serial/keyspan.c | 6
drivers/usb/serial/pl2303.c | 18 -
drivers/usb/serial/usb-serial.c | 38 +--
drivers/usb/serial/usb-serial.h | 2
drivers/usb/serial/visor.c | 48 ++--
drivers/usb/serial/whiteheat.c | 4
drivers/usb/storage/freecom.c | 4
drivers/usb/storage/transport.c | 307 -------------------------------
drivers/usb/storage/transport.h | 1
drivers/usb/storage/unusual_devs.h | 22 ++
include/linux/device.h | 36 ++-
53 files changed, 1047 insertions(+), 1231 deletions(-)
-----
ChangeSet@1.934, 2003-01-09 10:29:40-08:00, greg@kroah.com
USB: fix ehci build for older versions of gcc
drivers/usb/host/ehci-dbg.c | 32 ++++----------------------------
1 files changed, 4 insertions(+), 28 deletions(-)
------
ChangeSet@1.932, 2003-01-08 16:50:57-08:00, alan@lxorguk.ukuu.org.uk
[PATCH] PATCH: more unusual USB storage devices
IBM memory key
Epson 785EPX PCMCIA slot
Konica KD-200Z camera
drivers/usb/storage/unusual_devs.h | 22 ++++++++++++++++++++++
1 files changed, 22 insertions(+)
------
ChangeSet@1.897.1.8, 2003-01-08 10:21:15-08:00, neilt@slimy.greenend.org.uk
[PATCH] USB Serial patch for old pl2303 devices.
I got a PL2303 USB serial converter a few days ago, and got your driver
up and running fairly quickly. The problem is that I got an oops when I
rmmod-ed the drivers. The pl2303 uses two interfaces but registers only
the second (technically wrong, I guess, but should work). When pl2303.o
is removed, it attempts to deregister the first interface (which has no
effect), so the second interface remains registered with usbserial. The
old struct serial still points at the removed pl2303 driver so things go
pop when anything touches it.
I think the PL2303 hack in usb_serial_probe should not change the
"interface" variable, which gets stored in serial->interface, since
usbcore will register whatever "ifnum" says. I think that's enough
waffle. The patch is below. Keep up the good work!
drivers/usb/serial/usb-serial.c | 4 +---
1 files changed, 1 insertion(+), 3 deletions(-)
------
ChangeSet@1.897.1.7, 2003-01-08 10:09:32-08:00, henning@meier-geinitz.de
[PATCH] scanner.c, scanner.h: Use symbolic name for interface class
Hi,
On Wed, Jan 08, 2003 at 08:29:36AM -0800, Greg KH wrote:
> On Tue, Dec 24, 2002 at 05:44:55PM +0100, Henning Meier-Geinitz wrote:
> > Hi,
> >
> > On Tue, Dec 24, 2002 at 12:40:06AM +0100, Oliver Neukum wrote:
> > >
> > > > Well, the reason I didn't use one was that I didn't found one in
> > > > usb.h/usb_ch9.h for 16. It's also not listed on www.usb.org.
> > > >
> > > > lsusb calls it "Data". However, I'm not sure if this is a hex/dec
> > > > error and they really mean "Data" = dec 10, not 0x10 (=dec 16).
> > > >
> > > > Shall I define a local symbolic name (e.g.
> > > > STRANGE_HP_SCANJET_INTERFACE_CLASS)? But I really don't know what this
> > > > class is. I only know that it's used by a Hewlett-Packard ScanJet
> > > > 3300c and Genius HR6 USB - Vivid III.
> > >
> > > Better that than a bare number.
> >
> > Patch attached.
>
> Applied to my 2.4 tree, sorry for the delay.
Here is the same for 2.5.44:
drivers/usb/image/scanner.c | 2 +-
drivers/usb/image/scanner.h | 3 +++
2 files changed, 4 insertions(+), 1 deletion(-)
------
ChangeSet@1.897.1.6, 2003-01-08 09:32:25-08:00, baldrick@wanadoo.fr
[PATCH] USB: speedtouch: add GPL notices
speedtouch and friends: add GPL notices (yes, the module was released by Alcatel
under the GPL) and fix some typos.
drivers/usb/misc/atmsar.c | 146 +++++++++++++++++++++---------------------
drivers/usb/misc/atmsar.h | 27 +++++--
drivers/usb/misc/speedtouch.c | 72 ++++++++++++--------
3 files changed, 138 insertions(+), 107 deletions(-)
------
ChangeSet@1.897.1.5, 2003-01-08 09:32:04-08:00, duncan.sands@math.u-psud.fr
[PATCH] USB: speedtouch: remove version string duplication
speedtouch: remove udsl_version in favour of DRIVER_VERSION (which it duplicated).
drivers/usb/misc/speedtouch.c | 4 +---
1 files changed, 1 insertion(+), 3 deletions(-)
------
ChangeSet@1.897.1.4, 2003-01-08 09:31:41-08:00, baldrick@wanadoo.fr
[PATCH] USB: speedtouch missing __init and __exit
speedtouch: add __init and __exit to the module init/exit routines.
drivers/usb/misc/speedtouch.c | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
------
ChangeSet@1.897.1.3, 2003-01-08 09:31:20-08:00, baldrick@wanadoo.fr
[PATCH] USB: atmsar is not a module
atmsar is not a module in its own right, it is an auxiliary library for speedtouch.
So remove module code from atmsar and build module speedtch from speedtouch and
atmsar. Note the module name change speedtouch -> speedtch (speedtch is the name
used for the original 2.4 module, and is the name used in the online documentation).
drivers/usb/misc/Makefile | 6 +++---
drivers/usb/misc/atmsar.c | 31 -------------------------------
2 files changed, 3 insertions(+), 34 deletions(-)
------
ChangeSet@1.897.1.2, 2003-01-08 08:23:03-08:00, henning@meier-geinitz.de
[PATCH] [PATCH 2.5.54] scanner.c: endpoint detection cleanup
This patch makes endpoint detection more generic. Basically, only one bulk-in
endpoint is required, everything else is optional.
The patch is on top of the PV8630 removal patch.
drivers/usb/image/scanner.c | 55 ++++++++++++++++----------------------------
1 files changed, 21 insertions(+), 34 deletions(-)
------
ChangeSet@1.897.1.1, 2003-01-07 21:29:37-08:00, greg@kroah.com
Merge kroah.com:/home/linux/linux/BK/bleeding-2.5
into kroah.com:/home/linux/linux/BK/gregkh-2.5
include/linux/device.h | 24 ++++++++++++++----------
1 files changed, 14 insertions(+), 10 deletions(-)
------
ChangeSet@1.879.9.26, 2003-01-07 15:45:51-08:00, greg@kroah.com
[PATCH] USB serial: fixup for probe function paramaters changing.
drivers/usb/serial/visor.c | 4 ++--
drivers/usb/serial/whiteheat.c | 4 ++--
2 files changed, 4 insertions(+), 4 deletions(-)
------
ChangeSet@1.879.9.25, 2003-01-07 15:45:31-08:00, greg@kroah.com
[PATCH] USB serial: pass the usb_device_id to the probe() function
This is needed for drivers that want to use the driver_info field.
drivers/usb/serial/usb-serial.c | 2 +-
drivers/usb/serial/usb-serial.h | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
------
ChangeSet@1.879.9.24, 2003-01-07 15:34:35-08:00, henning@meier-geinitz.de
[PATCH] scanner.c, scanner.h: Remove PV8630 ioctls
This patch removes the inofficial ioctls that were used to support the
PV8630 USB-over-Parport chipset. They were alreaded ifdefed out.
Instead of them, the more generic (and official) SCANNER_IOCTL_CTRLMSG
should be used. The last software that used the old ioctl
(sane-hp4200) switched to the new ioctls a long time ago.
This patch is ontop of the "user-supplied" patch.
drivers/usb/image/scanner.c | 60 +-------------------------------------------
drivers/usb/image/scanner.h | 17 +-----------
2 files changed, 4 insertions(+), 73 deletions(-)
------
ChangeSet@1.879.9.23, 2003-01-07 15:22:11-08:00, pablo@menichini.com.ar
[PATCH] 2.5.54 dev_*(&<dev>,...): drivers/usb/input/pid.c
drivers/usb/input/pid.c | 45 +++++++++++++++------------------------------
1 files changed, 15 insertions(+), 30 deletions(-)
------
ChangeSet@1.879.9.22, 2003-01-07 15:10:35-08:00, henning@meier-geinitz.de
[PATCH] scanner.c: print user-supplied ids only on start-up
With this patch, information about user-supplied ids is printed only
once at startup instead of everytime any USB device is plugged in.
The patch is on top of the new ids patch.
drivers/usb/image/scanner.c | 8 ++++----
1 files changed, 4 insertions(+), 4 deletions(-)
------
ChangeSet@1.879.9.21, 2003-01-07 15:10:17-08:00, henning@meier-geinitz.de
[PATCH] scanner.c, scanner.h: Added vendor/product ids
This patch adds vendor/product ids for two Visioneer scanners.
The patch is on top of the ioctl patch.
drivers/usb/image/scanner.c | 5 ++++-
drivers/usb/image/scanner.h | 4 +++-
2 files changed, 7 insertions(+), 2 deletions(-)
------
ChangeSet@1.879.9.20, 2003-01-07 15:09:59-08:00, henning@meier-geinitz.de
[PATCH] USB scanner driver: updated Kconfig
This patch removes the link in Kconfig to
Documentation/usb/scanner-hp-sane.txt which was removed by the
documentation update.
drivers/usb/image/Kconfig | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
------
ChangeSet@1.879.9.19, 2003-01-07 15:09:40-08:00, henning@meier-geinitz.de
[PATCH] USB scanner driver: updated documentation
This patch updates the documentation for the USB scanner driver. The
details:
Documentation/usb/scanner.txt:
- Amended for linux-2.5.54
- Added information about read_timeout
- Added more details about /proc/bus/usb/devices
- Added/updated links
- Added pointers two "special" scanner drivers
- Reordering, spell-checking, formatting
- Used /dev/usb/scanner[0-15] instead of /dev/usbscanner[0-15]
- Removed some basic USB configuration stuff
- Added EHCI
- Removed some more references to HP
Documentation/usb/scanner-hp-sane.txt:
Removed completely. This was a very outdated text for some HP
scanners. All of this is explained in the documentation of the
user-space SANE tools. Links and a short explanation about SANE was
added to scanner.txt instead.
This is the (slightly adapted) patch you already apllied for 2.4.
Documentation/usb/scanner-hp-sane.txt | 79 --------
Documentation/usb/scanner.txt | 329 +++++++++++++---------------------
2 files changed, 134 insertions(+), 274 deletions(-)
------
ChangeSet@1.879.9.18, 2003-01-07 15:09:22-08:00, henning@meier-geinitz.de
[PATCH] scanner.c: fix race in ioctl_scanner()
This patch adds locking to ioctl_scanner() which was completely
lacking until now. The patch is originally from Oliver Neukum
<oliver@neukum.name>.
The patch was forward-ported from 2.4.
drivers/usb/image/scanner.c | 73 ++++++++++++++++++++++++++------------------
1 files changed, 44 insertions(+), 29 deletions(-)
------
ChangeSet@1.879.9.17, 2003-01-07 14:52:33-08:00, greg@kroah.com
[PATCH] USB: drivers/usb/serial/ fixups due to dev_printk change
drivers/usb/serial/bus.c | 9 +++---
drivers/usb/serial/empeg.c | 12 ++++----
drivers/usb/serial/ezusb.c | 4 +-
drivers/usb/serial/generic.c | 6 ++--
drivers/usb/serial/io_edgeport.c | 38 ++++++++++++-------------
drivers/usb/serial/io_ti.c | 58 +++++++++++++++++++--------------------
drivers/usb/serial/ir-usb.c | 16 +++++-----
drivers/usb/serial/keyspan.c | 6 ++--
drivers/usb/serial/pl2303.c | 18 ++++++------
drivers/usb/serial/usb-serial.c | 32 ++++++++++-----------
drivers/usb/serial/visor.c | 44 ++++++++++++++---------------
11 files changed, 122 insertions(+), 121 deletions(-)
------
ChangeSet@1.879.9.16, 2003-01-07 14:52:13-08:00, greg@kroah.com
[PATCH] USB: drivers/usb/host/ fixups due to dev_printk change
drivers/usb/host/ehci-dbg.c | 8 ++++----
drivers/usb/host/ohci-dbg.c | 22 +++++++++++-----------
drivers/usb/host/ohci-hcd.c | 10 +++++-----
drivers/usb/host/ohci-hub.c | 2 +-
drivers/usb/host/ohci-mem.c | 2 +-
drivers/usb/host/ohci-q.c | 4 ++--
6 files changed, 24 insertions(+), 24 deletions(-)
------
ChangeSet@1.879.9.15, 2003-01-07 14:51:54-08:00, greg@kroah.com
[PATCH] USB: drivers/usb/core/ fixups due to dev_printk change
drivers/usb/core/hcd-pci.c | 16 ++++-----
drivers/usb/core/hcd.c | 34 ++++++++++----------
drivers/usb/core/hub.c | 70 +++++++++++++++++++++----------------------
drivers/usb/core/usb-debug.c | 2 -
drivers/usb/core/usb.c | 38 +++++++++++------------
5 files changed, 80 insertions(+), 80 deletions(-)
------
ChangeSet@1.879.9.14, 2003-01-07 14:51:34-08:00, greg@kroah.com
[PATCH] DEV: change dev_printk() to take a pointer to dev instead of the structure itself.
This was suggested by many people, Randy Dunlap being the most vocal :)
include/linux/device.h | 12 ++++++------
1 files changed, 6 insertions(+), 6 deletions(-)
------
ChangeSet@1.879.9.13, 2003-01-07 12:59:07-08:00, greg@kroah.com
[PATCH] USB mdc800: forward port 2.4 fix for misuse of types.
Thanks to Dave Jones for pointing this out.
drivers/usb/image/mdc800.c | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
------
ChangeSet@1.879.9.12, 2003-01-07 12:57:25-08:00, greg@kroah.com
[PATCH] USB printer driver: forward port 2.4 fix for misuse of types.
Thanks to Dave Jones for pointing this out.
drivers/usb/class/usblp.c | 3 ++-
1 files changed, 2 insertions(+), 1 deletion(-)
------
ChangeSet@1.879.9.11, 2003-01-07 12:55:14-08:00, greg@kroah.com
[PATCH] USB: removed MOD_INC_USE_COUNT and MOD_DEC_USE_COUNT from driver that do not need it.
drivers/usb/misc/auerswald.c | 7 -------
drivers/usb/misc/brlvger.c | 18 +++++-------------
drivers/usb/misc/rio500.c | 5 +----
3 files changed, 6 insertions(+), 24 deletions(-)
------
ChangeSet@1.879.9.10, 2003-01-06 17:26:56-08:00, greg@kroah.com
USB brlvger: Forward port 2.4 fix for misuse of types.
Thanks to Dave Jones for pointing this out.
drivers/usb/misc/brlvger.c | 3 ++-
1 files changed, 2 insertions(+), 1 deletion(-)
------
ChangeSet@1.879.9.9, 2003-01-06 16:35:55-08:00, mdharm-usb@one-eyed-alien.net
[PATCH] USB storage: remove usb_stor_tranfer_length()
This patch removes the (often troublesome) usb_stor_transfer_length()
function.
We've finally gotten all the command initiators to send the correct values
in the srb->request_bufflen field, so this is no longer needed.
There are probably some sanity checks that can also be removed now, but
that's for a later patch.
drivers/usb/storage/freecom.c | 4
drivers/usb/storage/transport.c | 307 ----------------------------------------
drivers/usb/storage/transport.h | 1
3 files changed, 5 insertions(+), 307 deletions(-)
------
ChangeSet@1.879.9.8, 2003-01-06 16:31:07-08:00, greg@kroah.com
USB: revert davem's compile time fix, now that it's fixed properly.
drivers/usb/host/ohci-dbg.c | 2 +-
1 files changed, 1 insertion(+), 1 deletion(-)
------
ChangeSet@1.879.9.7, 2003-01-06 16:21:39-08:00, david-b@pacbell.net
[PATCH] usbtest, covers control queueing and fault cleanup
I wrote this a while back, finally debugged it. This covers
some functionality that 2.5 newly demands of all HCDs: control
requests can be queued. (Example: a user mode driver can talk
on one interface, and a kernel mode one can talk on another,
no need to handshake about who can make control requests.)
The good news is that all the HCDs seem (light testing) to do
the right things ... until some of the requests (intentionally)
trigger routine faults (like protocol stalls) which the HCDs
need to recover from. At that point, uhci-hcd started acting
confused (it's got newish queueing code); details will come
separately. The other two HCDs acted fine. I had expected more
trouble there, maybe it'll show up later on.
drivers/usb/misc/usbtest.c | 306 ++++++++++++++++++++++++++++++++++++++++++++-
1 files changed, 304 insertions(+), 2 deletions(-)
------
ChangeSet@1.879.9.6, 2003-01-06 16:21:21-08:00, david-b@pacbell.net
[PATCH] 2.5.54 -- ohci-dbg.c: 358: In function `show_list': `data1'
OK here's the version that without the kernel version #ifdef
that helped the backport ... it fixes the build by restoring
the "debug support only if CONFIG_USB_DEBUG" semantics.
drivers/usb/host/ohci-dbg.c | 11 +++++++++++
1 files changed, 11 insertions(+)
------
ChangeSet@1.879.9.5, 2003-01-06 16:01:14-08:00, oliver@neukum.name
[PATCH] USB: kaweth freeing skbs
this is the 2.5 version of the 2.4 fix
- proper freeing of skbs
drivers/usb/net/kaweth.c | 8 ++++----
1 files changed, 4 insertions(+), 4 deletions(-)
------
ChangeSet@1.879.9.4, 2003-01-06 15:58:15-08:00, petkan@users.sourceforge.net
[PATCH] again rtl8150
this diff is agains the latest linux-2.5;
set mac address at dev->open()
(as per Jeff Garzik :-)
drivers/usb/net/rtl8150.c | 5 ++++-
1 files changed, 4 insertions(+), 1 deletion(-)
------
ChangeSet@1.879.9.3, 2003-01-06 15:55:16-08:00, petkan@users.sourceforge.net
[PATCH] USB pegasus: small patch for 2.5
Same as the previous email, just against latest linux-2.5 tree. Sorry
about the diffs - i can't sync with usb-2.5.
drivers/usb/net/pegasus.c | 5 ++++-
drivers/usb/net/pegasus.h | 4 ++--
2 files changed, 6 insertions(+), 3 deletions(-)
------
ChangeSet@1.879.9.2, 2003-01-06 15:48:03-08:00, david-b@pacbell.net
[PATCH] zaurus B500 (sl-5600?) & usbnet
More Zaurii. That model will be interesting from the
perspective of "usb gadget drivers", lots of flexible
endpoints are available.
drivers/usb/net/usbnet.c | 22 ++++++++++++++++++++--
1 files changed, 20 insertions(+), 2 deletions(-)
------
ChangeSet@1.879.9.1, 2003-01-06 15:47:26-08:00, david-b@pacbell.net
[PATCH] ehci, remove potential hangs
These don't affect the hang I'm hunting for, but paranoia
argues the patch is better integrated than not:
- prevent resubmit-from-completion looping in_irq if the
transfers complete really fast. (likely never seen, but...)
- grab ehci lock before reading irq status; should be harmless
except in one host error cleanup-after-death
drivers/usb/host/ehci-hcd.c | 11 +++++++----
drivers/usb/host/ehci-q.c | 19 +++++++++++++------
drivers/usb/host/ehci.h | 2 ++
3 files changed, 22 insertions(+), 10 deletions(-)
------
^ permalink raw reply
* Re: Calling Application
From: Wolfgang Denk @ 2003-01-09 19:10 UTC (permalink / raw)
To: Aman; +Cc: linuxppc embedded
In-Reply-To: <001b01c2b810$7ec76720$370da8c0@aman>
In message <001b01c2b810$7ec76720$370da8c0@aman> you wrote:
>
> This might be a basic question. I have build the linux kernel for custom
> board which has PPC 440GP as its processor. I have also build my
> application. Now I wanted to call my application after the kernel boots up.
> Can you tell me where I hv to call my application.
Just like you start all other utility and server processes in Unix
systems: either you start it from one of your init scripts, or - in
case of simple systems - your application might even become the init
process.
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
"Life sucks, but it's better than the alternative."
- Peter da Silva
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply
* [PATCH] slab.c warnings
From: Stephen Hemminger @ 2003-01-09 19:17 UTC (permalink / raw)
To: Linus Torvalds; +Cc: Kernel Mailing List
This gets rid of the compiler warnings in mm/slab.c:
Example:
mm/slab.c: In function `slab_destroy':
mm/slab.c:806: warning: passing arg 1 of `__slab_error' discards
qualifiers from pointer target type
mm/slab.c:810: warning: passing arg 1 of `__slab_error' discards
qualifiers from pointer target type
diff -Nru a/mm/slab.c b/mm/slab.c
--- a/mm/slab.c Thu Jan 9 11:10:13 2003
+++ b/mm/slab.c Thu Jan 9 11:10:13 2003
@@ -502,7 +502,8 @@
#define slab_error(cachep, msg) __slab_error(__FUNCTION__, cachep, msg)
-static void __slab_error(char *function, kmem_cache_t *cachep, char
*msg)
+static void __slab_error(const char *function, kmem_cache_t *cachep,
+ const char *msg)
{
printk(KERN_ERR "slab error in %s(): cache `%s': %s\n",
function, cachep->name, msg);
^ permalink raw reply
* Re: MB without keyboard controller / USB-only keyboard ?
From: Pete Zaitcev @ 2003-01-09 19:16 UTC (permalink / raw)
To: Alan Cox; +Cc: linux-kernel
In-Reply-To: <mailman.1042135501.3903.linux-kernel2news@redhat.com>
>> > > pc_keyb: controller jammed (0xFF)
>> >
>> > Does your BIOS do keyboard emulation ?
>>
>> It is Compaq EVO D510. It has merely nothing of interest in the BIOS (no
>> keyboard emu). As far as I remember it contains an I845 chipset.
>
> Can you use the USB keyboard to configure the BIOS during boot. If so
> then it almost certainly has USB bios emulation. Another trivial test
> that would be useful is to stick a freedos boot floppy in the box and
> see if freedos works
I fail to see the point, Alan. Stephan's BIOS does exactly the
right thing: it emulates BIOS INTs which allow to read buffered
keystrokes, but it does not do SMM tricks to emulate port 0x60.
This is great, now pc_keyb.d must do detection right. It must
not loop endlessly if 0xff is returned from inb(). It's a bug.
-- Pete
^ permalink raw reply
* Re: [PATCH] Embed __this_module in module itself.
From: Richard B. Johnson @ 2003-01-09 19:16 UTC (permalink / raw)
To: Sam Ravnborg; +Cc: Miles Bader, Rusty Russell, linux-kernel
In-Reply-To: <20030109184935.GA11107@mars.ravnborg.org>
On Thu, 9 Jan 2003, Sam Ravnborg wrote:
> On Thu, Jan 09, 2003 at 10:18:53AM +0900, Miles Bader wrote:
> > Sam Ravnborg <sam@ravnborg.org> writes:
> > > Not knowing much about v850, I wonder why you do not need to set the -m
> > > option. Most other architectures do this.
> >
> > ???
> >
> > A far as I can see, no architecture does anything different than the
> > default.
>
> A little grepping gave the following result:
>
> i386/Makefile:LDFLAGS := -m elf_i386
> m68k/Makefile:LDFLAGS := -m m68kelf
> mips/Makefile:LDFLAGS := -G 0
> ppc64/Makefile:LDFLAGS := -m elf64ppc
> s390/Makefile:LDFLAGS := -m elf_s390
> s390x/Makefile:LDFLAGS := -m elf64_s390
> sh/Makefile:LDFLAGS := -EL
> sh/Makefile:LDFLAGS := -EB
> sparc/Makefile:LDFLAGS := -m elf32_sparc
> sparc64/Makefile:LDFLAGS := -m elf64_sparc
> x86_64/Makefile:LDFLAGS := -m elf_x86_64
>
> Little less than half of the architectures defines their own LDFLAGS.
> Most of them set an emulation, most probarly inherited from i386.
>
> >
> > [Why on earth would -m be needed, anyway?]
>
> I do not know, but as can be seen above several architectures use it.
>
>
> I have seen your proposed patch for gnu.linkonce.
> I do prefer to have it in arch/v850/Makefile because this is a workaround
> for an architecture specific bug in ld.
> Why not provide your own link script?
>
> Sam
The 'emulation' really defines the linker-script to use. The name
is pretty much a misnomer. Different architectures require different
linking parameters and you can force the linker to provide a `a.out`
(ZMAGIC) output as well as ELF.
Execute `ld -V` and the linker script will be displayed. If you
do `ld -V -m x` it will show the emulations provided, on ix86
machines, it's i386linux (for a.out) and elf_i386 (for ELF).
Cheers,
Dick Johnson
Penguin : Linux version 2.4.18 on an i686 machine (797.90 BogoMips).
Why is the government concerned about the lunatic fringe? Think about it.
^ permalink raw reply
* Re: [PATCH] PATCH: IPMI driver
From: Corey Minyard @ 2003-01-09 19:16 UTC (permalink / raw)
To: Alan Cox; +Cc: Dave Jones, Linux Kernel Mailing List
In-Reply-To: <1042135971.27796.44.camel@irongate.swansea.linux.org.uk>
Alan Cox wrote:
>On Thu, 2003-01-09 at 17:22, Dave Jones wrote:
>
>
>>On Thu, Jan 09, 2003 at 06:06:34PM +0000, Alan Cox wrote:
>>
>> > Arghhh I was told Linus accepted it, and my tree indexer found "IPMI" so
>> > decided it was present too. (Only the i2c definitions apparently).
>>
>>Shouldn't cause any problems in 2.4 anyways should it ?
>>After all, its 'just another driver'.
>>
>> > Oh well, it should be in 2.5
>>
>>Added to the queue of bits from the 2.4 changesets list that I'm
>>intending to push to Linus soon.
>>
>>
>
>Pull the 2.5 port from openipmi.sourceforge.net saves you doing the port
>yourself.
>
Definately pull the 2.5 port from there, as there are some differences
between the 2.4 and 2.5 versions.
-Corey
^ permalink raw reply
* RE: Kaaza 2 jammer.
From: Darrell Dieringer @ 2003-01-09 18:58 UTC (permalink / raw)
To: netfilter
In-Reply-To: <565759501.20030109180351@wp.pl>
I've always wondered something about the string matching, but never
having used it, I haven't researched it enough to know...
Wouldn't netfilter also see the string "KazzaClient" in this email
message? I can imagine how that might cause problems if the string
matching rules aren't well crafted.
I see in the example posted by Tomasz Wrona that it only applies to
tcp packets forwared from the internal interface, narrowing the focus
qiute a bit. But wouldn't that also block an email message having
that string if sent from an internal machine?
Of course, the sender of that message may have indeed sent it from a
client on his internal network, and since I'm reading it, it must have
worked as intended.
I imagine placing a string matching rule, like the example, _after_
rules which accept other legitimate traffic (like smtp) would work
completely fine.
Looking for eduction on the topic.
Darrell Dieringer - Madison, WI
> -----Original Message-----
> From: netfilter-admin@lists.netfilter.org
> [mailto:netfilter-admin@lists.netfilter.org]On Behalf Of
> Tomasz Wrona
> Sent: Thursday, January 09, 2003 11:04 AM
> To: netfilter@lists.samba.org
> Cc: lartc@mailman.ds9a.nl
> Subject: Kaaza 2 jammer.
>
>
> Hello,
>
> Some people asked about matching [blocking] Kaaza 2 sessions.
> So try this simple rule:
>
> iptables -I FORWARD -i $internal_interface -p tcp -m string
> --string "KazaaClient" -j REJECT --reject-with tcp-reset
> [Or maybe worth to try -j TARPIT]
>
> In above rule I don't specify separate ports due to dynamic
> port allocation.
> This rule works fine, catches and reset completly Kaaza 1 and 2
> versions.
>
>
> Regards,
> tw
^ permalink raw reply
* [parisc-linux] Trace/breakpoint trap
From: FARINATI,LEANDRO (HP-Brazil,ex1) @ 2003-01-09 18:57 UTC (permalink / raw)
To: Parisc-Linux List (E-mail)
Hi people,
The message "Trace/breakpoint trap" occurs to me when I execute my
application. This message occurs only when exists a break command or exists
another situation to occur this message?
Thanks in advance
-----------------------------------------------------------------------
Leandro Marcondes Farinati
Software Developer
* leandro.farinati@hp.com
^ permalink raw reply
* Re: Rage128 as secondary adapter
From: Jon Smirl @ 2003-01-09 18:56 UTC (permalink / raw)
To: Stefan Reinauer, fbdev
In-Reply-To: <20030109183921.GB21501@suse.de>
ATI has already released the much more sensitive data
of how to drive their Rage128 3D engine. It's all been
incorporated into X and is open source.
I doubt if the procedure for resetting the board is
considered a trade secret. The problem is in getting
ATIs attention long enough to tell how to do it. It
may be as simple as poking an output port with a
special value. Hopefully someone with a manual can
tell me.
=====
Jon Smirl
jonsmirl@yahoo.com
__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
^ permalink raw reply
* Calling Application
From: Aman @ 2003-01-09 18:54 UTC (permalink / raw)
To: linuxppc embedded
In-Reply-To: <1042053852.1207.176.camel@granite.austin.ibm.com>
Hi All
This might be a basic question. I have build the linux kernel for custom
board which has PPC 440GP as its processor. I have also build my
application. Now I wanted to call my application after the kernel boots up.
Can you tell me where I hv to call my application.
Thanking you in advance
Regards
Aman
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply
* Re: USB-storage/SCSI panic/error writing CF card
From: Patrick Mansfield @ 2003-01-09 18:53 UTC (permalink / raw)
To: linux-kernel, linux-scsi
In-Reply-To: <20030109183614.GA1167@Master.Wizards>
On Thu, Jan 09, 2003 at 01:36:14PM -0500, Murray J. Root wrote:
> Writing to the card sometimes hangs the process when unmounting
>
> Sometimes the data IS written to the card first, then it hangs the process.
>
> Sometimes the card is corrupt (cannot cd to the mountpoint -I/O error)
> /var/log/messages has several lines like:
> Jan 9 13:08:51 Master kernel: FAT: Filesystem panic (dev sd(8,1))
> Jan 9 13:08:51 Master kernel: Directory 4: invalid cluster chain
>
> Sometimes get kernel panic with ONLY these 2 lines:
> "Error handler thread not present at f7a57000 f7bf0d80 drivers/scsi/scsi-error.c 154"
> "In interrupt handler - not syncing"
> No messages in logs
The panic is caused by timeout on a scsi command when the error handler
has unexpectedly gone away, possibly because of this bug, where the erorr
handler exits early because of a SIGHUP:
http://marc.theaimsgroup.com/?l=linux-scsi&m=104145526331820&w=2
Fixing the panic won't fix the corruption. scsi should really offline the
adapter and scsi devices on the adapter rather than panic.
-- Patrick Mansfield
^ permalink raw reply
page: next (older) | prev (newer) | latest
- recent:[subjects (threaded)|topics (new)|topics (active)]
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.