All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans de Goede <j.w.r.degoede@hhs.nl>
To: kilgota@banach.math.auburn.edu
Cc: video4linux-list <video4linux-list@redhat.com>,
	sqcam-devel@lists.sourceforge.net
Subject: Re: [sqcam-devel] [REVIEW] Driver for SQ-905 based cameras
Date: Fri, 02 Jan 2009 08:55:42 +0100	[thread overview]
Message-ID: <495DC87E.2030007@hhs.nl> (raw)
In-Reply-To: <Pine.LNX.4.64.0901011539120.19217@banach.math.auburn.edu>

kilgota@banach.math.auburn.edu wrote:
> 
> 
> On Thu, 1 Jan 2009, Adam Baker wrote:
> 
>> On Thursday 01 January 2009, Hans de Goede wrote:
> 
>>>
>>> "\x0" will point to const memory, this is not allowed as a buffer 
>>> passed to
>>> usb_control_msg, instead you should use a r/w buffer suitable for DMA.
>>> We've got gspca_dev->usb_buf for this.
> 
> Perhaps my ignorance is showing here. If one actually specifies a value 
> to put into that slot, then why does it "point to const memory" and if 
> so why is that a sin? Sorry if you think this is a dumb question, but I 
> am a bit new to doing this kind of device support at the kernel level. 
> In userspace stuff like libgphoto2 such things are obviously of much 
> less significance.
> 

Well for one const memory is read only and usb_control_msg might try to write 
to it. Another problem is that usb_control_msg() needs a dma-able buffer. In 
kernelspace not all memory is equal. In this case the memory needs to match 
certain alignment criteria and might need to be in a certain physical address 
range (ISA for example can not do dma to physical addresses above 16 megabyte, 
32 bit PCI devices cannot do dma above 4 Gigabyte, etc.).

Regards,

Hans

--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

  parent reply	other threads:[~2009-01-02  7:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-01  0:33 [REVIEW] Driver for SQ-905 based cameras Adam Baker
2009-01-01  6:11 ` Alexey Klimov
2009-01-01 12:28 ` Hans de Goede
2009-01-01 21:19   ` [sqcam-devel] " Adam Baker
     [not found]     ` <Pine.LNX.4.64.0901011539120.19217@banach.math.auburn.edu>
2009-01-02  7:55       ` Hans de Goede [this message]
2009-01-01 17:38 ` Jean-Francois Moine
     [not found]   ` <Pine.LNX.4.64.0901011220230.18838@banach.math.auburn.edu>
2009-01-01 20:48     ` Adam Baker

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=495DC87E.2030007@hhs.nl \
    --to=j.w.r.degoede@hhs.nl \
    --cc=kilgota@banach.math.auburn.edu \
    --cc=sqcam-devel@lists.sourceforge.net \
    --cc=video4linux-list@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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.