From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from scorpius.homelinux.org (unknown [213.219.165.150]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by ozlabs.org (Postfix) with ESMTP id E016567B9D for ; Thu, 20 Jul 2006 17:21:40 +1000 (EST) Date: Thu, 20 Jul 2006 09:21:34 +0200 From: Marc Leeman To: Kumar Gala Subject: Re: [PATCH] Add USB to MPC8349 PB platform support Message-ID: <20060720072134.GX5219@scorpius.homelinux.org> References: <4879B0C6C249214CBE7AB04453F84E4D050B55@zch01exm20.fsl.freescale.net> <4856A73A-BB23-4850-A697-1CE7C385DE42@kernel.crashing.org> <1E6652B1-3126-4B69-BE9D-8DCE8DCACE7C@embeddedalley.com> <20060719201941.GW5219@scorpius.homelinux.org> <4AC92920-4642-4899-B8CA-8EE5A1CDE0B3@kernel.crashing.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="5LZCLy8Sy7WgNZQM" In-Reply-To: <4AC92920-4642-4899-B8CA-8EE5A1CDE0B3@kernel.crashing.org> Cc: linuxppc-dev@ozlabs.org Reply-To: Marc Leeman List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , --5LZCLy8Sy7WgNZQM Content-Type: text/plain; charset=iso-8859-15 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable > >Though I do agree that there is a gap: it would be nice to have some > >place to submit the kernel patches; >=20 > This should be the kernel. The general rule of thumb I've used is if =20 > its useful to more than one other person its worth trying to get into =20 > the kernel. However, I can see if you are doing a one off kernel for=20 That is about the same rule that I use; luckily (a credit to the Linux kernel and other developers); I don't have to change much stuff like that. =20 > your embedded product that getting your changes into the kernel =20 > wouldn't be worth while. You have to have a desire to interact with =20 > the community if you want to get your code in. There is a grey zone, but let's talk about a specific case: In my current queue, I have to write a Host Port Interface (HPI) protocol (serial) to a TI DSP. I would imagine that this is a useful contribution. However, using HPI is almost by nature limited to specific embedded designs (most of which differ slightly from one another). Furthermore; I will need to use a number of GPIO pins on a 834x processor. Using this needs to be backed by configuration settings in U-Boot. If someone else makes a similar design; it would most likely be with another processor family; and even then; they'll have other pins connected/used. Though the protocol would be a real nice addition; the physical connection/configuration make including it in the main kernel tree difficult. > Personally, I see it useful if for no other reason that someone will =20 > fixup my board port if/when they change something which will make my =20 > moving to a newer kernel release that much easier. Even though I would welcome this; our boards are included in larger expensive systems that would just be shipped back in case of problems; but we've never had functional (linux) problems (yet). Come to think of it, I have a number of minor patches for 8349SYS based configurations; where can I find the last devel code (next to 2.6.17) for patch creation (and to whom to send them back)? --=20 greetz, marc If you must address me, do so as Your Supreme Eminence. Which you should be doing anyway. Rygel - Throne for a Loss scorpius.homelinux.org 2.6.17 #2 PREEMPT Thu Jun 22 07:18:33 CEST 2006 GNU/= Linux --5LZCLy8Sy7WgNZQM Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEvy7+UQpj09NWLeERAl1CAJ9vRX2sxikKkr128G3MWSqGjMUw7QCeKEA+ t5KOTznI/HCMl84vGUSVfZ8= =zgVD -----END PGP SIGNATURE----- --5LZCLy8Sy7WgNZQM--