On Mon, Dec 04, 2023 at 05:15:36PM +0800, Chen Wang wrote: > > On 2023/12/4 7:32, Inochi Amaoto wrote: > > > On 2023/12/2 0:21, Conor Dooley wrote: > > > As far as I know, sophgo's SoC product names all start with "sg", while products starting with "cv" come from CVITEK (another chip company). CVITEK was acquired by sophgo a year ago, so now many SOC product names that originally started with "cv" are being repackaged and changed to start with "sg". > > > > > > For the cv1800b adopted by Duo, Sophgo has made it clear that it will not change its codename. > > > > > > But I heard that for other products, such as the cv1812h used by Huashanpi, sophgo may change their names in the future, but sophgo has not officially confirmed it yet. Looks like sophgo themselves are still in the process of digesting cv's products, ;) > > > > > > Since we have just started to support cv1812h and have not done much work yet, I suggest not to merge this patch into the mainline, and wait until there is clear news before doing this to avoid introducing unnecessary modifications later. > > > > > Hi Chen, > > > > There is a update for you. The cv1812h does not have the A53 core as the > > sg200x does. Maybe we should treat cv1812h as a trim of sg200x, not just > > a reband. > > > > According to this information, I suggest to preserve these code for > > cv1812h, it can make upstream the new soc eaiser. Also, adding a new > > compatible is not too hard, and it is necessary if we have new soc. > > Otherwise, the one with Huashan Pi now may be confused because it have > > a old version. > > Thanks Inochi for your info, let's just preserve these code for huashan pi > now and keep watching on what's going on then. Could you explain on what you mean by "preserve"? I'm a little unsure.
Attachment:
signature.asc
Description: PGP signature
