ARM Sunxi Platform Development
 help / color / mirror / Atom feed
From: Andre Przywara <andre.przywara@arm.com>
To: Shivam Gupta <gupta.shivam1996@gmail.com>
Cc: "linux-sunxi@lists.linux.dev" <linux-sunxi@lists.linux.dev>
Subject: Re: [PATCH] add Eachlink H6 Mini
Date: Thu, 8 May 2025 17:05:07 +0100	[thread overview]
Message-ID: <20250508170507.3d426494@donnerap.manchester.arm.com> (raw)
In-Reply-To: <SJ1PR12MB6313678B38CB96D3C24FECE5A08BA@SJ1PR12MB6313.namprd12.prod.outlook.com>

On Thu, 8 May 2025 15:41:34 +0000
Shivam Gupta <gupta.shivam1996@gmail.com> wrote:

> Hi,
> While following the instructions to the letter on
> https://linux-sunxi.org/New_Device_howto, I sent the wrong patch. Wanted
> to add a fex file for an A10 tablet (https://linux-sunxi.org/Softwinners_crane)
> It's the next patch I sent after that.

Ah, I see. Unfortunately those instructions are somewhat outdated. I don't
think sunxi-boards is really maintained anymore, at best FEX files are
somewhat irrelevant for mainline, even Allwinner seems to have dropped
that ball many years ago.

> As a beginner I did exactly what it said, git add and send patch, but
> didn't git commit as it didn't say that anywhere, I'm sorry for that.

Yeah, I see that it proposes to send a patch to the list. Which is
somewhat pointless, as it's a github based repo, so it should follow that
process there.

> For an A10 tablet, should I still send a pull request over github or the
> email method is fine?

For that old tablet I think you can push the FEX file, via a Github PR,
though I don't know many people care about this still.
If your aim is to run (mainline) Linux, you would need a devicetree file
anyway. You can use the information in the FEX to create or generate one.

Cheers,
Andre

> https://lore.kernel.org/linux-sunxi/20250508150811.7046-1-gupta.shivam1996@gmail.com/T/#u
> 
> Thanks,
> 
> Shivam
> 
> ________________________________
> From: Andre Przywara <andre.przywara@arm.com>
> Sent: Thursday, May 8, 2025 8:55:30 pm
> To: Shivam Gupta <gupta.shivam1996@gmail.com>
> Cc: linux-sunxi@lists.linux.dev <linux-sunxi@lists.linux.dev>;
> hundertzwei <46927478+hundertzwei@users.noreply.github.com> Subject: Re:
> [PATCH] add Eachlink H6 Mini
> 
> On Thu,  8 May 2025 20:04:11 +0530
> Shivam Gupta <gupta.shivam1996@gmail.com> wrote:
> 
> Hi,
> 
> > From: hundertzwei <46927478+hundertzwei@users.noreply.github.com>
> >
> > extracted from miniH6-public-3Gddr-20181113-update.img
> > ---  
> 
> what repository is this against? I guess sunxi-boards.git on
> github.com/linux-sunxi?
> 
> This doesn't use an email based contribution process, so please send a
> pull-request via github.
> 
> Not sure how useful a FEX file for an H6 based device is anyway, but I
> guess it doesn't hurt...
> 
> Cheers,
> Andre.
> 


  parent reply	other threads:[~2025-05-08 16:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-08 14:34 [PATCH] add Eachlink H6 Mini Shivam Gupta
2025-05-08 15:25 ` Andre Przywara
     [not found]   ` <SJ1PR12MB6313678B38CB96D3C24FECE5A08BA@SJ1PR12MB6313.namprd12.prod.outlook.com>
2025-05-08 16:05     ` Andre Przywara [this message]
     [not found]       ` <SJ1PR12MB6313123CC3D9C79C9E51BF93A090A@SJ1PR12MB6313.namprd12.prod.outlook.com>
2025-05-15  9:23         ` Andre Przywara
2025-05-15 13:15           ` Shivam Gupta

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=20250508170507.3d426494@donnerap.manchester.arm.com \
    --to=andre.przywara@arm.com \
    --cc=gupta.shivam1996@gmail.com \
    --cc=linux-sunxi@lists.linux.dev \
    /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