RE: [PATCH 0/5] DSPBRIDGE: patches.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

> Ok, so we have:
> a) omapzoom bridge
> b) linux omap bridge
> 
> Impertinent question: what are our plans b/w these two?
> 

A. omapzoom bridge -- As far as I know, this will be the master tree for the DSPBridge code. The Bridge patches will be based on this tree. I think it was already communicated some time ago that the linux-omap mailing list will be used for Bridge discussions and for sending the Bridge patches to OMAPZOOM. There is no separate mailing list for omapzoom.

B. linux omap bridge -- I think this tree is maintained by Hiroshi by merging the patches that are sent to OMAPZOOM tree. The only difference that should be between the omapzoom tree and linux omap tree is the Power management. Omapzoom Bridge uses T.I Power management, where as the linux omap Bridge uses open source Power management. So, any patches related to open source power manaegment will be based on linux omap tree. The maintainer of linux omap Bridge tree should sync up the Bridge changes from the omapzoom tree.


Thank you,
Best regards,
Hari
 

> -----Original Message-----
> From: Menon, Nishanth 
> Sent: Thursday, March 05, 2009 8:05 AM
> To: Kanigeri, Hari; Felipe Contreras
> Cc: Ameya Palande; Guzman Lugo, Fernando; Hiroshi DOYU; 
> linux-omap@xxxxxxxxxxxxxxx
> Subject: RE: [PATCH 0/5] DSPBRIDGE: patches.
> 
> Hi Hari,
> > -----Original Message-----
> > From: linux-omap-owner@xxxxxxxxxxxxxxx [mailto:linux-omap- 
> > owner@xxxxxxxxxxxxxxx] On Behalf Of Kanigeri, Hari
> > Sent: Thursday, March 05, 2009 3:52 PM
> > To: Felipe Contreras
> > Cc: Ameya Palande; Guzman Lugo, Fernando; Hiroshi DOYU; linux- 
> > omap@xxxxxxxxxxxxxxx
> > Subject: RE: [PATCH 0/5] DSPBRIDGE: patches.
> > > We are in linux-omap, not omapzoom, and this is the tidspbridge 
> > > branch in linux-omap:
> > > http://git.kernel.org/?p=linux/kernel/git/tmlind/linux-omap-2.
> > 6.git;a=shortlog;h=tidspbridge
> > >
> > > I'm sure you don't want to increase the discrepancy between 
> > > linux-omap and omapzoom, so the patches sent to l-o 
> should apply on 
> > > top of the l-o tidspbridge in order to be merged.
> > 
> > -- I am sorry, as of now the Bridge patches will be based only on 
> > omapzoom tree.
> 
> Ok, so we have:
> a) omapzoom bridge
> b) linux omap bridge
> 
> Impertinent question: what are our plans b/w these two?
> 
> Regards,
> Nishanth Menon
> --
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Arm (vger)]     [ARM Kernel]     [ARM MSM]     [Linux Tegra]     [Linux WPAN Networking]     [Linux Wireless Networking]     [Maemo Users]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux