That explains it - Here you go
-Original Message-
From: Hans Petter Selasky [mailto:hsela...@c2i.net]
Sent: 11 February 2009 09:01
To: freebsd-usb@freebsd.org; Andrew Thompson
Cc: Thomas Sparrevohn
Subject: Re: Recent Changes to Rum driver - seems to have..
On Tuesday 10 February 2009
Ok will do - Just need to get out of "Vista land" - so it will take a little
while
-Original Message-
From: Hans Petter Selasky [mailto:hsela...@c2i.net]
Sent: 11 February 2009 15:17
To: Thomas Sparrevohn
Cc: freebsd-usb@freebsd.org; 'Andrew Thompson'
Subject: Re: R
ky
Cc: freebsd-usb@freebsd.org; Thomas Sparrevohn
Subject: Re: Recent Changes to Rum driver - seems to have..
On Wed, Feb 11, 2009 at 10:00:45AM +0100, Hans Petter Selasky wrote:
> On Tuesday 10 February 2009, Thomas Sparrevohn wrote:
> > Reintroduced panics when the device is used hea
Hi
I have a bit of a problem - I have a Dell XPS 710 H2C using the
nforce 590 for Intel chipset -
unfortunately I no longer have any PS/2 keyboards which make this
mail somewhat unproductive.
but here the case In both PAE and AMD64 versions Current the USB base
buses fail to attach - I in
lto:[EMAIL PROTECTED] On Behalf Of John Baldwin
Sent: 20 February 2007 16:47
To: [EMAIL PROTECTED]
Cc: Thomas Sparrevohn; freebsd-usb@freebsd.org
Subject: Re: USB fails to attach in the SMP version of GENERIC with Nforce
590
On Saturday 17 February 2007 16:34, Thomas Sparrevohn wrote:
> HI
>
The following reply was made to PR usb/109274; it has been noted by GNATS.
From: "Thomas Sparrevohn" <[EMAIL PROTECTED]>
To: "'John Baldwin'" <[EMAIL PROTECTED]>,
<[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Subject: RE: amd64/109274:
The following reply was made to PR usb/109274; it has been noted by GNATS.
From: "Thomas Sparrevohn" <[EMAIL PROTECTED]>
To: "'John Baldwin'" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Subject: RE: amd64/109274: MCP55 USB Controller fails to attac
On 20 Feb 2007, at 21:12, John Baldwin wrote:
On Tuesday 20 February 2007 13:42, Thomas Sparrevohn wrote:
Yes - I am always normally running CURRENT - It was when I
couldn't get USB
to work
I tried with the 6.2 Image I had installed from and was surprised to
discover it worked
Unde
Petter, John and Warner - If you need
anything tested the system is not currently being used for anything
permanent so
I be happy to help in any way
In message: <[EMAIL PROTECTED]>
Hans Petter Selasky <[EMAIL PROTECTED]> writes:
: On Tuesday 20 February 2007 20:10, Thoma
I had a similar problem with the AMD64 version and changing to the new USB
stack solved the problem
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Hans Petter Selasky
Sent: 01 March 2007 08:13
To: freebsd-usb@freebsd.org
Subject: Re: amd64 usb error=4 int
On Monday 28 May 2007 21:17:29 M. Warner Losh wrote:
> In message: <[EMAIL PROTECTED]>
> Anish Mistry <[EMAIL PROTECTED]> writes:
> : What requirements still need to be met before the HPS USB stack is
> : committed to CURRENT?
>
> It will go into the into the tree when it is ready
Hi
I am currently trying to pin down a problem with the native USB stack on the
AMD64 -
when I am booting in 64bit mode with the MCP55 USB stack it fails in usb_attach
- so
far the only clear error I have found is that the first Unit is not found
correctly - below is the 32BIT
debug output
Thanks - Thanks - I am very very pleased to inform you that the MCP55 USB
native USB stack now attaches correctly under
the AMD64 and all my USB devices seems to work - I believe that I had a GNAT
problem
report about it that can be closed
Thanks a million
due to the segment has been
overwritten/changed/freed while the ATA driver was holding the same tag
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Thomas Sparrevohn
Sent: 13 October 2008 22:08
To: 'Søren Schmidt'; [EMAIL PROTECTED]
Subject: Out
I downloaded the release candidate 2 for the new USB stack and while it work
very well for most things
I am getting repeated panics when using heavy disk traffic - I believe the
issue is related to the
problems I described in the "out of bounce buffers mail" - Yet with the new
stack it show up
On Sunday 26 October 2008 15:33:20 Hans Petter Selasky wrote:
What is the device naming change to?
> Hi,
>
> A new USB release is available:
>
> http://www.selasky.org/hans_petter/usb4bsd/for_review/
>
> %md5 usb2_release_003.*
> MD5 (usb2_release_003.diff) = e31a032d0234bb7d72eb968c33118d84
On Friday 31 October 2008 14:14:59 Hans Petter Selasky wrote:
> On Friday 31 October 2008, Thomas Sparrevohn wrote:
> > On Sunday 26 October 2008 15:33:20 Hans Petter Selasky wrote:
> >
> >
> > What is the device naming change to?
>
> The device names un
On Friday 31 October 2008 15:29:59 Hans Petter Selasky wrote:
Will do - Thanks a million I give u. feedback
___
freebsd-usb@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to "[EMAIL PROTECTED]
On Friday 31 October 2008 15:56:42 Hans Petter Selasky wrote:
> On Friday 31 October 2008, Olivier SMEDTS wrote:
> > Hello,
> >
> > Each device driver has been splitted since RC3.
> > Look in /boot/kernel/usb2_*. You can use modules.
> > For example, for my usb mouse, I use usb2_input_ums.
>
> Hi,
On Wednesday 05 November 2008 08:15:52 Hans Petter Selasky wrote:
> Hi,
>
> > And one last thing:
> > # usbdevs -v
> > usbdevs: no USB controllers found
> >
>
> That command is no longer supported. Use "usbconfig" instead. I'm not sure if
> it is currently installed by default.
>
> --HPS
>
us
> > see attached fault - In short the problem has been around for a long time
> > but it seems to be related to the USB stack DMA handling - before usb2
> > it showed up as a DMA error in the ATA driver - but that was because
> > the old umass driver somehow "stole" an active DMA
> >
> > {gigantic
I have a 4GB SDHC card that I have formatted with ufs and installed a current
kernel on - Its connected to a USB reader.
Now here is the thing - I can boot the kernel with USB2 well enough but when it
comes to mount root - it looks like
USB2 has not probed and attached the device yet and I get
On Saturday 10 January 2009 15:23:48 Olivier SMEDTS wrote:
The patch works for me and allows me to boot - however eventually I get the
usb2_pc_common_mem_cb:429: Page offset was not preserved!
Error - I wonder if the error is specific to the Nvidia Nforce 590 Intel
chipset or its more generic a
On Saturday 10 January 2009 18:40:10 Hans Petter Selasky wrote:
>
> It is chipset independent. It appears at the moment data is bounced, because
> you have too much memory in the computer :-) Currently the USB drivers only
> supports 32-bits of DMA addressing.
>
> --HPS
>
Well I guess its n
Before we switch GENERIC - would it be possibly to have the bus dma issue
committed as well? Without the patch manually added none of my umass devices
work under amd64
-Original Message-
From: owner-freebsd-...@freebsd.org [mailto:owner-freebsd-...@freebsd.org]
On Behalf Of Alfred Perlste
On Friday 06 February 2009 15:19:01 M. Warner Losh wrote:
> Doesn't the busdma issue need to be solved before we do this? usb2
> currently doesn't work if you have memory above 4GB due to this
> issue. I thought we tagged it as a show stopper for making it the
> default.
>
> Warner
To be honst
Reintroduced panics when the device is used heavily - it also reports the
"needs callback" in dmesg - Unless this is known I can post a dmesg
___
freebsd-usb@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe
27 matches
Mail list logo
