From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stefan Richter Subject: Re: [PATCH 1/2] ALSA: add LaCie Firewire Speakers/Griffin FireWave surround driver Date: Mon, 7 Feb 2011 17:49:19 +0100 Message-ID: <20110207174919.43b85e16@stein> References: <4D46933D.5050609@ladisch.de> <4D4FB7C8.7090501@ladisch.de> <4D4FB7F6.8000801@ladisch.de> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4D4FB7F6.8000801@ladisch.de> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: linux1394-devel-bounces@lists.sourceforge.net To: Clemens Ladisch Cc: alsa-devel@alsa-project.org, linux1394-devel@lists.sourceforge.net, Jay Fenlason List-Id: alsa-devel@alsa-project.org On Feb 07 Clemens Ladisch wrote: > + static const struct device_info lacie_speakers = { > + .driver_name = "FWSpeakers", > + .short_name = "Firewire Speakers", > + .long_name = "LaCie Firewire Speakers", FWIW, it is spelled "LaCie FireWire Speakers" in LaCie's printed material and on their web site, whereas their firmware programmers put "LaCie Firewire speakers" as model descriptor leaf into the Configuration ROM. Does the precise case of device_info strings matter to userspace? -- Stefan Richter -=====-==-== --=- --=== http://arcgraph.de/sr/ ------------------------------------------------------------------------------ The modern datacenter depends on network connectivity to access resources and provide services. The best practices for maximizing a physical server's connectivity to a physical network are well understood - see how these rules translate into the virtual world? http://p.sf.net/sfu/oracle-sfdevnlfb