From: Joshua Kinard <kumba@gentoo.org>
To: gentoo-mips@lists.gentoo.org
Subject: Re: [gentoo-mips] SGI Octane kernel patch available
Date: Tue, 23 Sep 2014 17:57:22 -0400 [thread overview]
Message-ID: <5421ECC2.6060604@gentoo.org> (raw)
In-Reply-To: <CADnq5_P77kryEyZDBeqA5KvCzuOhqg39ZY4BSp1=oUS2o0mbJw@mail.gmail.com>
On 09/23/2014 09:16, Alex Deucher wrote:
> On Mon, Sep 22, 2014 at 8:00 PM, Joshua Kinard <kumba@gentoo.org> wrote:
>> On 09/22/2014 10:44, Alex Deucher wrote:
>>> On Mon, Sep 22, 2014 at 5:47 AM, Joshua Kinard <kumba@gentoo.org> wrote:
>>>> I've made a unified patch against linux-3.16.0 available to get Octane working
>>>> for anyone with such a machine again. I still have to re-work the patchset for
>>>> mips-sources to include this, but that will take a while longer. I'll try to
>>>> get stages uploaded in a few days someplace as well, along with the minimal
>>>> netboot initramfs.
>>>>
>>>> Full info is available here on the forums:
>>>> https://forums.gentoo.org/viewtopic-p-7621340.html
>>>>
>>>
>>> For review purposes and probably a better chance of spotting bugs, it
>>> would be nice if you could break you patch up into manageable pieces
>>> and send then out as git patches. E.g., precursor patches, core
>>> support patches, individual new driver patches.
>>>
>>> Alex
>>
>> The goal is to eventually get this into linux-mips upstream by breaking it up
>> into separate patches for review. Right now, though, I just wanted to put
>> something out there for others to hack on and maybe improve things. There are
>> still some drivers that Octane uses that can work on other systems that have
>> problems on those other systems. Specifically, the IOC3 metadriver. That
>> doesn't work on IP27 right now, and that's the bare minimum that has to be
>> fixed before I can send things upstream, since upstream won't accept two
>> different variants of IOC3 code for two different systems.
>
> IMHO, it's easier for others to contribute and improve things if you
> break the patch up. Some one familiar with the ioc3 hw may take the
> time to look at a few ioc3 patches, but quickly get discouraged trying
> to sift through a huge patch that touches tons of unrelated things.
> You might also want to provide a git tree so others can easily grab
> the changes.
>
> Just my 2 cents.
Agreed completely. I'm just a bit disorganized in my hacking and haven't sat
down to fully separate the various bits up into logical components and drop
them into a git tree. It's on the TODO list, because I'll need git's
capabilities to eventually organize things into a patch set to send upstream
(and I have to look into quilt, too).
--
Joshua Kinard
Gentoo/MIPS
kumba@gentoo.org
4096R/D25D95E3 2011-03-28
"The past tempts us, the present confuses us, the future frightens us. And our
lives slip away, moment by moment, lost in that vast, terrible in-between."
--Emperor Turhan, Centauri Republic
prev parent reply other threads:[~2014-09-23 21:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-22 9:47 [gentoo-mips] SGI Octane kernel patch available Joshua Kinard
2014-09-22 14:44 ` Alex Deucher
2014-09-23 0:00 ` Joshua Kinard
2014-09-23 13:16 ` Alex Deucher
2014-09-23 21:57 ` Joshua Kinard [this message]
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=5421ECC2.6060604@gentoo.org \
--to=kumba@gentoo.org \
--cc=gentoo-mips@lists.gentoo.org \
/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