On Jul 10, 2013, at 1:42 PM, "Steven Hartland" wrote:
>
> - Original Message ----- From: "Justin T. Gibbs"
>> On Jul 10, 2013, at 1:06 PM, "Steven Hartland" wrote:
>>> - Original Message - From: "Justin T. Gibbs"
>>
On Jul 10, 2013, at 1:06 PM, "Steven Hartland" wrote:
> - Original Message - From: "Justin T. Gibbs"
>> I'm sure lots of folks have "some solution" to this. Here is an
>> old version of what we use at Spectra:
>> http://people.fr
On Jul 10, 2013, at 11:21 AM, Xin Li wrote:
> Signed PGP part
> On 07/10/13 02:02, Dag-Erling Smrgrav wrote:
> > The attached patch causes ZFS to base the minimum transfer size for
> > a new vdev on the GEOM provider's stripesize (physical sector size)
> > rather than sectorsize (logical sector
>It appears that there is no support for the Adaptec 2903b SCSI card, but of
>course I could be wrong. I would like to get this card to work, so if anyone
>could point me to a painfully obvious url or some documentation on how to
>get it to work that I have clearly overlooked, I would be forever
>> I changed the code locally a while back to allocate the table during
>> the allocation of the dma tag. This seems to work, but I just haven't
>> gotten back to it to think through all of the consequences. Whatever
>> the solution, we don't want to device a solution where most drivers
>> have
>Hi all,
>
>Currently bus_dmamap_load builds the dma descriptor in a table on the
>stack.
>This cause us following problems:
> . our dma can be large, 1MB or more, this forces us to increase the
>kernel stack size.
> . our hardware would be happy with the dma descriptors as they are,
> address and
>
>There are a couple of rules in PCI you must have in mind when
>synchronization between PCI devices is needed.
>
>1) Interrupts are not synchronization events. They just send attention to
> the device driver (acts as SIGIO, for example). Some bridge may flush
> posted buffers on interrupt, b
>>Does the FreeBSD tcp stack do zero copy (page flip the data to
>>userspace)? In the localhost case, it seems like there are two copies
>>to/from userspace there.
>
> It has the ability to do it via sendfile() and a few other mechanisms, but
>not as a normal part of typical read()/write().
A
>It appears things are more complicated than that. I have swapped
>the Adaptec 29160 for a 2940UW. I am now running continous buildworlds,
>a 'dd' of the SCSI disk and fxtv in parallel.
>
>This appears to work like a charm until now. I'll let it run and
>see what develops
I bet you the aic7892 o
>On Fri, Nov 02, 2001 at 12:21:22AM +0100, Wilko Bulte wrote:
>
>I forgot to mention that I had the same config running fine
>on the same Abit MB using 4.3-stable.
In 4.3-stable, we ignored the parity errors due to a logic bug.
--
Justin
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsu
>
>> The fact that the data is less than a page in size matters little
>> to the bus dma concept. In other words, how is this packet presented
>> to the hardware? Does it care that all of the component pieces are
>> < PAGE_SIZE in length? Probably not. It just wants the list of
>> address/leng
>> >My understanding is that you need a dmamap for every buffer that you want
>> >to map into bus space.
>>
>> You need one dmamap for each independantly manageable mapping. A
>> single mapping may result in a long list of segments, regardless
>> of whether you have a single KVA buffer or multip
>
>Correction.
>
>This sample:
>>
>> if (bus_dma_tag_create(pci->parent_dmat, PAGE_SIZE, lim,
>> BUS_SPACE_MAXADDR, BUS_SPACE_MAXADDR, NULL, NULL, len, 1,
>> BUS_SPACE_MAXSIZE_32BIT, 0, &pci->cntrol_dmat) != 0) {
>> isp_prt(isp, ISP_LOGERR,
>>
>Every hear the phrase "you get what you pay for?" The API isn't all that
>clear, and we don't have a man page or document that describes in detail
>how to use it properly. Rather than whining about that, I decided to
>tinker with it and Use The Source, Luke (tm). This is the result.
Fair enough.
>
>It's reasonable to want to control what get's called FreeBSD.
>
Certainly. But I think it has to go beyond the installer. We
should define an environment that third party applications can
depend on being available in any installation that claims to
be FreeBSD. Without this, you have the sam
The Foundation has yet to approach Wind River about the Trademark,
so I cannot speculate on their disposition.
>>>
>>>What are your plans to change this situation?
>>
>>The Foundation isn't planning to do anything about the trademark or
>>in regards to any of its other proposed activitie
>> The Foundation has yet to approach Wind River about the Trademark,
>> so I cannot speculate on their disposition.
>
>What are your plans to change this situation?
The Foundation isn't planning to do anything about the trademark or
in regards to any of its other proposed activities until suffic
>Hackers, CC [EMAIL PROTECTED]
>
>Wind River might be cautious & slow when considering donating the
>FreeBSD trademark to a FreeBSD Foundation controlled by a board of
>just 3 directors, that even FreeBSD people are just getting to know
>of, & have yet to evaluate as `The Foundation'.
I believe t
> A couple of months ago IBM released the source to their linux modem
>driver for the thinkpad 600 & 600E:
I was looking to port this stuff to -current, so I'd be interested
in seeing your patches. It would be nice if we could simply
rewrite the kernel portion of the code to avoid the GPL lice
>> >Each link is checked once every second to see if the link is still up.
>> >An attempt to send a packet over a dead link will cause the packet to
>> >be shifted over to the next link in the bundle.
>>
>> Any chance this can be done through an async event rather
>> than by polling?
>
>If there
>Each link is checked once every second to see if the link is still up.
>An attempt to send a packet over a dead link will cause the packet to
>be shifted over to the next link in the bundle.
Any chance this can be done through an async event rather
than by polling?
--
Justin
To Unsubscribe: s
>
>On Fri, 9 Mar 2001, Mike Smith wrote:
>
>> Joe; it looks like you have some funny ideas about something that's not
>> actually very relevant. I assume that you have already gone and bought
>> Monster Cable(tm) SCSI cables, and that you have the special
>> oxygen-free-copper SCSI controller
>i did the vinum stuff again, but now im getting all kind of errors.
>btw, the kernel is of this morning (4.2 cvsuped this morning - local time), i
>noticed some fixes to the aic7xxx.
You have a bad cable or terminator. The 7899 runs quite a bit faster
than the 2940U, so the problem may not hav
>: Just so I'm completely clear on this though, the intent is that multiple
>: bus_alloc_resource calls for a single BAR within a single driver is
>: explictly prohibited, right? So if I want to map ONLY the first byte
>: and the last byte of, say, a 16MB PCI BAR, I have to map the whole
>: thing
>I'm on FreeBSD 4.1.1 and when I attempt multiple calls to
>bus_alloc_resource on a PCI device for the same BAR, I run afoul of code
>in resource_list_alloc:
>
>rle = resource_list_find(rl, type, *rid);
>
>if (!rle)
>return 0; /* no resource of that type/rid */
>i
>Justin,
>
> Thanks for your prompt response, but I did see the 3.3 release
>notes, before attempting the install. It does say that
>"Adaptec AIC7850, AIC7860, AIC7880, AIC789x, on-board SCSI controllers."
>are supported. Btw, the release notes for 3.4 also says the same.
>
> Can anyon
> I bought 3.3 CD's from Walnut Creek and use BSD at home, but that
>has a IDE disk. This is my first attempt at installing one with SCSI.
>Upgrading to 4.x is not an option.
FreeBSD 3.3 does not include support for the 7892.
IIRC 3.4 and all releases after it, supports the 7892.
--
Justi
>I've got a Belkin OmniView Pro 8-Port KVM switch which thinks it's
>much smarter than it really is.
I've had so many problems with this product that I dumped it for
an Apex Outlook. I couldn't be happier.
Since I donated the Belkin to another group, I've heard that they
were able to send it in
As some of you may know, I'm working on a 501(c)3 (tax exempt/non-profit)
determination for the FreeBSD Foundation. The IRS seems to be a little
confused about the nature of FreeBSD and we're currenlty working on
a response to an initial determination from the IRS that was not
favorable. One thi
In article <[EMAIL PROTECTED]> you wrote:
> Current FreeBSD SCSi disk naming mechanism is problem for using more than
> one disks in the chain during the disk failure.
>
> The problem is that the name is not fixed with is SCSI ID. e.g.,
> if one disk is presented in the chain, regardless its SCSI
>> > /*lowaddr*/BUS_SPACE_MAXADDR_32BIT,
>> > /*highaddr*/BUS_SPACE_MAXADDR,
>>
>> low and high address of the region that the DMA engine cannot access.
>
>Meaning e.g. the 16Mbyte barrier that ISA DMA has?
>For PCI this would be
>> > /*lowaddr*/BUS_SPACE_MAXADDR_32BIT,
>> > /*highaddr*/BUS_SPACE_MAXADDR,
>>
>> low and high address of the region that the DMA engine cannot access.
>
>Meaning e.g. the 16Mbyte barrier that ISA DMA has?
>For PCI this would b
>> bus_dma related stuff is only required if the device has a DMA engine
>> you wish to use. To access the shared memory on the card (e.g. map
>
>Eh, sorry, I was confused. It has *both* shared memory and a DMA engine.
>
>> it into the kernel's virtual address space), you will need to use
>> the r
>> bus_dma related stuff is only required if the device has a DMA engine
>> you wish to use. To access the shared memory on the card (e.g. map
>
>Eh, sorry, I was confused. It has *both* shared memory and a DMA engine.
>
>> it into the kernel's virtual address space), you will need to use
>> the
In article <199907201904.vaa03...@yedi.iaf.nl> you wrote:
> I'm currently trying to hack a driver together for a PCI card that uses
> shared memory to communicate to the host.
>
> If I'm not completely offtrack I need to use (under newbus/-current)
> bus_dma_tag_create, bus_dma_alloc etc to get ac
In article <[EMAIL PROTECTED]> you wrote:
> I'm currently trying to hack a driver together for a PCI card that uses
> shared memory to communicate to the host.
>
> If I'm not completely offtrack I need to use (under newbus/-current)
> bus_dma_tag_create, bus_dma_alloc etc to get access to the car
> How do you think about some MO(Magneto Otpical disk) and PD drives?
>
> 3.5" 650MB and 1.3GB MO drives should handle 512KB/sector(128MB,
> 230MB, 540MB) and 2048KB/sector media(640MB, 1.3GB).
The da driver should handle 2048KB sector sized media right now. If
it doesn't for some reason, that i
> How do you think about some MO(Magneto Otpical disk) and PD drives?
>
> 3.5" 650MB and 1.3GB MO drives should handle 512KB/sector(128MB,
> 230MB, 540MB) and 2048KB/sector media(640MB, 1.3GB).
The da driver should handle 2048KB sector sized media right now. If
it doesn't for some reason, that
This stuff should really go to the SCSI list. I read that list much more
frequently than this one.
> The Iomega USB Zip drive is a bit slow when resetting (reset of the USB
> part of the drive). It takes 1s or more to reset. The reset is initiated
> because for example an illegal command was rece
This stuff should really go to the SCSI list. I read that list much more
frequently than this one.
> The Iomega USB Zip drive is a bit slow when resetting (reset of the USB
> part of the drive). It takes 1s or more to reset. The reset is initiated
> because for example an illegal command was rec
40 matches
Mail list logo
