linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Josh Boyer <jwboyer@linux.vnet.ibm.com>
To: "Prodyut Hazarika" <phazarika@amcc.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: Question on 4xx GIT tree
Date: Wed, 10 Sep 2008 20:31:00 -0400	[thread overview]
Message-ID: <20080910203100.6c0bf2d5@zod.rchland.ibm.com> (raw)
In-Reply-To: <0CA0A16855646F4FA96D25A158E299D605014C18@SDCEXCHANGE01.ad.amcc.com>

On Wed, 10 Sep 2008 16:47:48 -0700
"Prodyut Hazarika" <phazarika@amcc.com> wrote:

> Hi Josh,
> I have few questions.
> 
> > > Should I base my patch from your master branch or your 'next' branch?
> > The 'next' branch would be best.
> 
> I saw that both your master and next branches have removed the 4xx dma and USB drivers.
> The dma drivers for 4xx used to under: drivers/dma/ppc440spe-adma.c
> The usb driver for 4xx used to be under: drivers/usb/gadget/dwc_otg/*
> The whole dwc_otg directory got removed.

Those drivers were never in any version of the upstream kernel
according to git.

[jwboyer@yoda linux-2.6]$ git checkout master
Switched to branch "master"
[jwboyer@yoda linux-2.6]$ git log -- drivers/dma/ppc440spe-adma.c
[jwboyer@yoda linux-2.6]$ git log -- drivers/usb/gadget/dwc_otg
[jwboyer@yoda linux-2.6]$

> Do you know the reason why these drivers were removed? Also, are there plans to get these drivers back?
> Please let me know.

Perhaps they are in the DENX kernel?  If so, someone would need to
submit them for inclusion.

josh

  reply	other threads:[~2008-09-11  0:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-08 20:55 Question on 4xx GIT tree Prodyut Hazarika
2008-09-08 21:35 ` Josh Boyer
2008-09-08 21:42   ` Prodyut Hazarika
2008-09-08 23:38     ` Josh Boyer
2008-09-10 23:47       ` Prodyut Hazarika
2008-09-11  0:31         ` Josh Boyer [this message]
2008-09-11  0:34           ` Prodyut Hazarika
2008-09-11  4:48             ` Stefan Roese

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=20080910203100.6c0bf2d5@zod.rchland.ibm.com \
    --to=jwboyer@linux.vnet.ibm.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=phazarika@amcc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).