On 03/02/24 17:45:42, Yang Xiwen wrote: > On 2/3/2024 4:32 PM, Jorge Ramirez-Ortiz, Gmail wrote: > > On 03/02/24 07:54:22, Shawn Guo wrote: > > > On Sat, Feb 3, 2024 at 5:44 AM Igor Opaniuk <[email protected]> > > > wrote: > > > > > > > > Add myself as co-maintainer for Poplar board, as I'm currently > > > > working on it (re-testing releases, addressing issues etc). > > > > > > > > CC: Jorge Ramirez-Ortiz <[email protected]> > > > > CC: Shawn Guo <[email protected]> > > > > Signed-off-by: Igor Opaniuk <[email protected]> > > > > > > Acked-by: Shawn Guo <[email protected]> > > > > > > I'm not actively working on poplar any more, so maybe remove me in the > > > meantime. > > > > > > hi Igor, > > > > Yes please go ahead and thanks for offering. > > > > I'll sync with you later next week (I found my Poplar in storage, so maybe > > we cam improve things a little) > > Also it would be good if we knew there are still users. > > > > > > Acked-by: Jorge Ramirez-Ortiz <[email protected]> > > > Hi, everyone. I'm working on a set-top box with a Hi3798MV200 SoC. It is > very similar to the Hi3798CV200 SoC and many peripherals and drivers can be > reused. I think you can try moving arch/arm/include/asm/arch-hi3798cv200 to > arch/arm/mach-histb and let's maintain all HiSTB series SoCs/boards under it > altogether? The same thing also applies to TF-A. Currently upstream code > refers to poplar everywhere but actually the port is portable enough to > handle a lot of other Hi3798-series SoCs such as Hi3798MV2x, Hi3798MV3x > etc..
Sure, if this is indeed a family we should do that (documentation was scarce back them when I did the initial port). maybe you'd like to take a stab Igor? > > > > > > Shawn >
