In one post, you mention getting a public git tree accesible:
"Patch was generated using git. Looks like, it's essential for me to
publicly host git repository for OpenRD that folks can clone until
patches are accepted in mainline/in-tree."
Tinker and myself are both eager for this tree. It would be greatly
appreciated if you could get the OpenRD tree public.
> In one post, you mention getting a public git tree accesible:
> "Patch was generated using git. Looks like, it's essential for me to
> publicly host git repository for OpenRD that folks can clone until
> patches are accepted in mainline/in-tree."
> Tinker and myself are both eager for this tree. It would be greatly
> appreciated if you could get the OpenRD tree public.
This would be very welcome for me, too.
I wonder why the marvell git tree from the sheevaplug kernel isn't used for openrd (base/client), too?
> I wonder why the marvell git tree from the sheevaplug kernel isn't used for openrd (base/client), too?
git.marvell.com does get OpenRD patches, and its what i've been using,
but I think theres some latency before the work gets pulled in on the
marvell tree.
Github has certain interesting features to keep track, fork repositories; storage space is limitation. repo.or.cz may work out well assuming git being hosted on this server earlier. Any thought ?
Second, baseline repo - kernel.org or Nicholas' orion.git. Nicholas being upstream maintainer, all patches will go through him.
Looking forward to your feedback or suggestions based on past experience.
- Dhaval
rektide wrote: >> I wonder why the marvell git tree from the sheevaplug kernel isn't used for openrd (base/client), too?
> git.marvell.com does get OpenRD patches, and its what i've been using, > but I think theres some latency before the work gets pulled in on the > marvell tree.
-- _____________________________________________________________________ Disclaimer: This e-mail message and all attachments transmitted with it are intended solely for the use of the addressee and may contain legally privileged and confidential information. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution, copying, or other use of this message or its attachments is strictly prohibited. If you have received this message in error, please notify the sender immediately by replying to this message and please delete it from your computer. Any views expressed in this message are those of the individual sender unless otherwise stated.Company has taken enough precautions to prevent the spread of viruses. However the company accepts no liability for any damage caused by any virus transmitted by this email. _____________________________________________________________________
yeah not really sure why openrd has forked to a seperate project
really, can't the sheevaplug & openrd be in the same project as from a
software perspective they must look almost identical.
On Aug 24, 12:23 pm, rektide <rekt...@gmail.com> wrote:
> > I wonder why the marvell git tree from the sheevaplug kernel isn't used for openrd (base/client), too?
> git.marvell.com does get OpenRD patches, and its what i've been using,
> but I think theres some latency before the work gets pulled in on the
> marvell tree.
> yeah not really sure why openrd has forked to a seperate project
> really, can't the sheevaplug & openrd be in the same project as from a
> software perspective they must look almost identical.
> On Aug 24, 12:23 pm, rektide <rekt...@gmail.com> wrote:
> > > I wonder why the marvell git tree from the sheevaplug kernel isn't used for openrd (base/client), too?
> > git.marvell.com does get OpenRD patches, and its what i've been using,
> > but I think theres some latency before the work gets pulled in on the
> > marvell tree.
> Github has certain interesting features to keep track, fork
> repositories; storage space is limitation. repo.or.cz may work out well
> assuming git being hosted on this server earlier. Any thought ?
> Second, baseline repo - kernel.org or Nicholas' orion.git. Nicholas
> being upstream maintainer, all patches will go through him.
> Looking forward to your feedback or suggestions based on past experience.
> - Dhaval
> rektide wrote:
> >> I wonder why the marvell git tree from the sheevaplug kernel isn't used for openrd (base/client), too?
> > git.marvell.com does get OpenRD patches, and its what i've been using,
> > but I think theres some latency before the work gets pulled in on the
> > marvell tree.
> --
> _____________________________________________________________________
> Disclaimer: This e-mail message and all attachments transmitted with it
> are intended solely for the use of the addressee and may contain legally
> privileged and confidential information. If the reader of this message
> is not the intended recipient, or an employee or agent responsible for
> delivering this message to the intended recipient, you are hereby
> notified that any dissemination, distribution, copying, or other use of
> this message or its attachments is strictly prohibited. If you have
> received this message in error, please notify the sender immediately by
> replying to this message and please delete it from your computer. Any
> views expressed in this message are those of the individual sender
> unless otherwise stated.Company has taken enough precautions to prevent
> the spread of viruses. However the company accepts no liability for any
> damage caused by any virus transmitted by this email.
> _____________________________________________________________________
> Just wondering if there is an update on some sort of central repo for > OpenRD?
> Andrew,
> On Aug 27, 3:23 pm, seddona <sedd...@googlemail.com> wrote: >> yeah not really sure why openrd has forked to a seperate project >> really, can't the sheevaplug & openrd be in the same project as from a >> software perspective they must look almost identical.
>> On Aug 24, 12:23 pm, rektide <rekt...@gmail.com> wrote:
>>>> I wonder why the marvell git tree from the sheevaplug kernel isn't used for openrd (base/client), too? >>> git.marvell.com does get OpenRD patches, and its what i've been using, >>> but I think theres some latency before the work gets pulled in on the >>> marvell tree.
-- _____________________________________________________________________ Disclaimer: This e-mail message and all attachments transmitted with it are intended solely for the use of the addressee and may contain legally privileged and confidential information. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution, copying, or other use of this message or its attachments is strictly prohibited. If you have received this message in error, please notify the sender immediately by replying to this message and please delete it from your computer. Any views expressed in this message are those of the individual sender unless otherwise stated.Company has taken enough precautions to prevent the spread of viruses. However the company accepts no liability for any damage caused by any virus transmitted by this email. _____________________________________________________________________
> On Aug 27, 6:54 am, Dhaval Vasa <dhaval.v...@einfochips.com> wrote:
>> For past couple of days, I have been evaluating appropriate home for
>> OpenRD git repository - linux, u-boot.
>> Github has certain interesting features to keep track, fork
>> repositories; storage space is limitation. repo.or.cz may work out well
>> assuming git being hosted on this server earlier. Any thought ?
>> Second, baseline repo - kernel.org or Nicholas' orion.git. Nicholas
>> being upstream maintainer, all patches will go through him.
>> Looking forward to your feedback or suggestions based on past experience.
>> - Dhaval
>> rektide wrote:
>>>> I wonder why the marvell git tree from the sheevaplug kernel isn't used for openrd (base/client), too?
>>> git.marvell.com does get OpenRD patches, and its what i've been using,
>>> but I think theres some latency before the work gets pulled in on the
>>> marvell tree.
>> --
>> _____________________________________________________________________
>> Disclaimer: This e-mail message and all attachments transmitted with it
>> are intended solely for the use of the addressee and may contain legally
>> privileged and confidential information. If the reader of this message
>> is not the intended recipient, or an employee or agent responsible for
>> delivering this message to the intended recipient, you are hereby
>> notified that any dissemination, distribution, copying, or other use of
>> this message or its attachments is strictly prohibited. If you have
>> received this message in error, please notify the sender immediately by
>> replying to this message and please delete it from your computer. Any
>> views expressed in this message are those of the individual sender
>> unless otherwise stated.Company has taken enough precautions to prevent
>> the spread of viruses. However the company accepts no liability for any
>> damage caused by any virus transmitted by this email.
>> _____________________________________________________________________
-- _____________________________________________________________________
Disclaimer: This e-mail message and all attachments transmitted with it
are intended solely for the use of the addressee and may contain legally
privileged and confidential information. If the reader of this message
is not the intended recipient, or an employee or agent responsible for
delivering this message to the intended recipient, you are hereby
notified that any dissemination, distribution, copying, or other use of
this message or its attachments is strictly prohibited. If you have
received this message in error, please notify the sender immediately by
replying to this message and please delete it from your computer. Any
views expressed in this message are those of the individual sender
unless otherwise stated.Company has taken enough precautions to prevent
the spread of viruses. However the company accepts no liability for any
damage caused by any virus transmitted by this email.
_____________________________________________________________________
> Expect one by tomorrow. I was evaluating different hosting sites.
> - Dhaval
> seddona wrote:
> > Hi Dhaval,
> > Just wondering if there is an update on some sort of central repo for
> > OpenRD?
> > Andrew,
> > On Aug 27, 3:23 pm, seddona <sedd...@googlemail.com> wrote:
> >> yeah not really sure why openrd has forked to a seperate project
> >> really, can't the sheevaplug & openrd be in the same project as from a
> >> software perspective they must look almost identical.
> >> On Aug 24, 12:23 pm, rektide <rekt...@gmail.com> wrote:
> >>>> I wonder why the marvell git tree from the sheevaplug kernel isn't used for openrd (base/client), too?
> >>> git.marvell.com does get OpenRD patches, and its what i've been using,
> >>> but I think theres some latency before the work gets pulled in on the
> >>> marvell tree.
> --
> _____________________________________________________________________
> Disclaimer: This e-mail message and all attachments transmitted with it
> are intended solely for the use of the addressee and may contain legally
> privileged and confidential information. If the reader of this message
> is not the intended recipient, or an employee or agent responsible for
> delivering this message to the intended recipient, you are hereby
> notified that any dissemination, distribution, copying, or other use of
> this message or its attachments is strictly prohibited. If you have
> received this message in error, please notify the sender immediately by
> replying to this message and please delete it from your computer. Any
> views expressed in this message are those of the individual sender
> unless otherwise stated.Company has taken enough precautions to prevent
> the spread of viruses. However the company accepts no liability for any
> damage caused by any virus transmitted by this email.
> _____________________________________________________________________
-- _____________________________________________________________________ Disclaimer: This e-mail message and all attachments transmitted with it are intended solely for the use of the addressee and may contain legally privileged and confidential information. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution, copying, or other use of this message or its attachments is strictly prohibited. If you have received this message in error, please notify the sender immediately by replying to this message and please delete it from your computer. Any views expressed in this message are those of the individual sender unless otherwise stated.Company has taken enough precautions to prevent the spread of viruses. However the company accepts no liability for any damage caused by any virus transmitted by this email. _____________________________________________________________________
-- _____________________________________________________________________ Disclaimer: This e-mail message and all attachments transmitted with it are intended solely for the use of the addressee and may contain legally privileged and confidential information. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution, copying, or other use of this message or its attachments is strictly prohibited. If you have received this message in error, please notify the sender immediately by replying to this message and please delete it from your computer. Any views expressed in this message are those of the individual sender unless otherwise stated.Company has taken enough precautions to prevent the spread of viruses. However the company accepts no liability for any damage caused by any virus transmitted by this email. _____________________________________________________________________
I was planning to submit the openrd-base platform support to upstream U-boot quite soon now. I've been waiting for a set of patches needed for UBIFS support to get accepted upstream, which looks like it should happen any day now:
> --
> _____________________________________________________________________
> Disclaimer: This e-mail message and all attachments transmitted with it
> are intended solely for the use of the addressee and may contain legally
> privileged and confidential information. If the reader of this message
> is not the intended recipient, or an employee or agent responsible for
> delivering this message to the intended recipient, you are hereby
> notified that any dissemination, distribution, copying, or other use of
> this message or its attachments is strictly prohibited. If you have
> received this message in error, please notify the sender immediately by
> replying to this message and please delete it from your computer. Any
> views expressed in this message are those of the individual sender
> unless otherwise stated.Company has taken enough precautions to prevent
> the spread of viruses. However the company accepts no liability for any
> damage caused by any virus transmitted by this email.
> _____________________________________________________________________
since it's fork of existing linux-2.6.git; you will see contact as I push changes. So how, there is little technical issue which is getting resolved today.
>> haunma wrote: >>> Ok.... so..... what happened? >>> Mark >> --
-- _____________________________________________________________________ Disclaimer: This e-mail message and all attachments transmitted with it are intended solely for the use of the addressee and may contain legally privileged and confidential information. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution, copying, or other use of this message or its attachments is strictly prohibited. If you have received this message in error, please notify the sender immediately by replying to this message and please delete it from your computer. Any views expressed in this message are those of the individual sender unless otherwise stated.Company has taken enough precautions to prevent the spread of viruses. However the company accepts no liability for any damage caused by any virus transmitted by this email. _____________________________________________________________________
>> haunma wrote:
>>> Ok.... so..... what happened?
>>> Mark
>> --
>> _____________________________________________________________________
>> Disclaimer: This e-mail message and all attachments transmitted with it
>> are intended solely for the use of the addressee and may contain legally
>> privileged and confidential information. If the reader of this message
>> is not the intended recipient, or an employee or agent responsible for
>> delivering this message to the intended recipient, you are hereby
>> notified that any dissemination, distribution, copying, or other use of
>> this message or its attachments is strictly prohibited. If you have
>> received this message in error, please notify the sender immediately by
>> replying to this message and please delete it from your computer. Any
>> views expressed in this message are those of the individual sender
>> unless otherwise stated.Company has taken enough precautions to prevent
>> the spread of viruses. However the company accepts no liability for any
>> damage caused by any virus transmitted by this email.
>> _____________________________________________________________________
-- _____________________________________________________________________
Disclaimer: This e-mail message and all attachments transmitted with it
are intended solely for the use of the addressee and may contain legally
privileged and confidential information. If the reader of this message
is not the intended recipient, or an employee or agent responsible for
delivering this message to the intended recipient, you are hereby
notified that any dissemination, distribution, copying, or other use of
this message or its attachments is strictly prohibited. If you have
received this message in error, please notify the sender immediately by
replying to this message and please delete it from your computer. Any
views expressed in this message are those of the individual sender
unless otherwise stated.Company has taken enough precautions to prevent
the spread of viruses. However the company accepts no liability for any
damage caused by any virus transmitted by this email.
_____________________________________________________________________
> >> Will be applying openrd specific patches now!
> >> - Dhaval
> >> haunma wrote:
> >>> Ok.... so..... what happened?
> >>> Mark
> >> --
> >> _____________________________________________________________________
> >> Disclaimer: This e-mail message and all attachments transmitted with it
> >> are intended solely for the use of the addressee and may contain legally
> >> privileged and confidential information. If the reader of this message
> >> is not the intended recipient, or an employee or agent responsible for
> >> delivering this message to the intended recipient, you are hereby
> >> notified that any dissemination, distribution, copying, or other use of
> >> this message or its attachments is strictly prohibited. If you have
> >> received this message in error, please notify the sender immediately by
> >> replying to this message and please delete it from your computer. Any
> >> views expressed in this message are those of the individual sender
> >> unless otherwise stated.Company has taken enough precautions to prevent
> >> the spread of viruses. However the company accepts no liability for any
> >> damage caused by any virus transmitted by this email.
> >> _____________________________________________________________________
> --
> _____________________________________________________________________
> Disclaimer: This e-mail message and all attachments transmitted with it
> are intended solely for the use of the addressee and may contain legally
> privileged and confidential information. If the reader of this message
> is not the intended recipient, or an employee or agent responsible for
> delivering this message to the intended recipient, you are hereby
> notified that any dissemination, distribution, copying, or other use of
> this message or its attachments is strictly prohibited. If you have
> received this message in error, please notify the sender immediately by
> replying to this message and please delete it from your computer. Any
> views expressed in this message are those of the individual sender
> unless otherwise stated.Company has taken enough precautions to prevent
> the spread of viruses. However the company accepts no liability for any
> damage caused by any virus transmitted by this email.
> _____________________________________________________________________
On Sep 8, 9:04 pm, Dhaval Vasa <dhaval.v...@einfochips.com> wrote:
> since it's fork of existing linux-2.6.git; you will see contact as I
> push changes. So how, there is little technical issue which is getting
> resolved today.
(this is against a fully up-to-date linux GIT checkout).
I selected the OpenRD Base as the only machine in the kernel
menuconfig.
I get this error:
arch/arm/mach-kirkwood/openrd_base-setup.c:76: error:
‘MACH_TYPE_OPENRD_BASE’ undeclared here (not in a function)
make[1]: *** [arch/arm/mach-kirkwood/openrd_base-setup.o] Error 1
Seems there is a commit to the include files missing (mach-types.h)?
Same error happened when I checkout out the marvell orion tree, btw.
> On Sep 8, 9:04 pm, Dhaval Vasa <dhaval.v...@einfochips.com> wrote: >> since it's fork of existing linux-2.6.git; you will see contact as I >> push changes. So how, there is little technical issue which is getting >> resolved today.
> (this is against a fully up-to-date linux GIT checkout).
> I selected the OpenRD Base as the only machine in the kernel > menuconfig.
> I get this error: > arch/arm/mach-kirkwood/openrd_base-setup.c:76: error: > ‘MACH_TYPE_OPENRD_BASE’ undeclared here (not in a function) > make[1]: *** [arch/arm/mach-kirkwood/openrd_base-setup.o] Error 1
> Seems there is a commit to the include files missing (mach-types.h)?
> Same error happened when I checkout out the marvell orion tree, btw.
> Regards,
> Leon.
-- _____________________________________________________________________ Disclaimer: This e-mail message and all attachments transmitted with it are intended solely for the use of the addressee and may contain legally privileged and confidential information. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution, copying, or other use of this message or its attachments is strictly prohibited. If you have received this message in error, please notify the sender immediately by replying to this message and please delete it from your computer. Any views expressed in this message are those of the individual sender unless otherwise stated.Company has taken enough precautions to prevent the spread of viruses. However the company accepts no liability for any damage caused by any virus transmitted by this email. _____________________________________________________________________
> > >> Will be applying openrd specific patches now!
> > >> - Dhaval
> > >> haunma wrote:
> > >>> Ok.... so..... what happened?
> > >>> Mark
> > >> --
> > >> _____________________________________________________________________
> > >> Disclaimer: This e-mail message and all attachments transmitted with it
> > >> are intended solely for the use of the addressee and may contain legally
> > >> privileged and confidential information. If the reader of this message
> > >> is not the intended recipient, or an employee or agent responsible for
> > >> delivering this message to the intended recipient, you are hereby
> > >> notified that any dissemination, distribution, copying, or other use of
> > >> this message or its attachments is strictly prohibited. If you have
> > >> received this message in error, please notify the sender immediately by
> > >> replying to this message and please delete it from your computer. Any
> > >> views expressed in this message are those of the individual sender
> > >> unless otherwise stated.Company has taken enough precautions to prevent
> > >> the spread of viruses. However the company accepts no liability for any
> > >> damage caused by any virus transmitted by this email.
> > >> _____________________________________________________________________
> > --
> > _____________________________________________________________________
> > Disclaimer: This e-mail message and all attachments transmitted with it
> > are intended solely for the use of the addressee and may contain legally
> > privileged and confidential information. If the reader of this message
> > is not the intended recipient, or an employee or agent responsible for
> > delivering this message to the intended recipient, you are hereby
> > notified that any dissemination, distribution, copying, or other use of
> > this message or its attachments is strictly prohibited. If you have
> > received this message in error, please notify the sender immediately by
> > replying to this message and please delete it from your computer. Any
> > views expressed in this message are those of the individual sender
> > unless otherwise stated.Company has taken enough precautions to prevent
> > the spread of viruses. However the company accepts no liability for any
> > damage caused by any virus transmitted by this email.
> > _____________________________________________________________________
>> Just curious what your plans are for keeping in sync with Marvell
>> patches and also synching with upstream?
>> Thanks
>> On Sep 9, 9:43 am, Dhaval Vasa <dhaval.v...@einfochips.com> wrote:
>>> You can check now. I will be adding OpenRD client related patches as well.
>>> - Dhaval
>>> tinker wrote:
>>>> Nothing seems to be there. I see no content.
>>>> On Sep 8, 3:28 am, Dhaval Vasa <dhaval.v...@einfochips.com> wrote:
>>>>> Initial clone is done at:
>>>>> http://repo.or.cz/w/linux-2.6-openrd.githttp://repo.or.cz/w/u-boot-op...
>>>>> Will be applying openrd specific patches now!
>>>>> - Dhaval
>>>>> haunma wrote:
>>>>>> Ok.... so..... what happened?
>>>>>> Mark
>>>>> --
>>>>> _____________________________________________________________________
>>>>> Disclaimer: This e-mail message and all attachments transmitted with it
>>>>> are intended solely for the use of the addressee and may contain legally
>>>>> privileged and confidential information. If the reader of this message
>>>>> is not the intended recipient, or an employee or agent responsible for
>>>>> delivering this message to the intended recipient, you are hereby
>>>>> notified that any dissemination, distribution, copying, or other use of
>>>>> this message or its attachments is strictly prohibited. If you have
>>>>> received this message in error, please notify the sender immediately by
>>>>> replying to this message and please delete it from your computer. Any
>>>>> views expressed in this message are those of the individual sender
>>>>> unless otherwise stated.Company has taken enough precautions to prevent
>>>>> the spread of viruses. However the company accepts no liability for any
>>>>> damage caused by any virus transmitted by this email.
>>>>> _____________________________________________________________________
>>>> Email Scanned for Virus & Dangerous Content by :www.CleanMailGateway.com >>> --
>>> _____________________________________________________________________
>>> Disclaimer: This e-mail message and all attachments transmitted with it
>>> are intended solely for the use of the addressee and may contain legally
>>> privileged and confidential information. If the reader of this message
>>> is not the intended recipient, or an employee or agent responsible for
>>> delivering this message to the intended recipient, you are hereby
>>> notified that any dissemination, distribution, copying, or other use of
>>> this message or its attachments is strictly prohibited. If you have
>>> received this message in error, please notify the sender immediately by
>>> replying to this message and please delete it from your computer. Any
>>> views expressed in this message are those of the individual sender
>>> unless otherwise stated.Company has taken enough precautions to prevent
>>> the spread of viruses. However the company accepts no liability for any
>>> damage caused by any virus transmitted by this email.
>>> _____________________________________________________________________
-- _____________________________________________________________________
Disclaimer: This e-mail message and all attachments transmitted with it
are intended solely for the use of the addressee and may contain legally
privileged and confidential information. If the reader of this message
is not the intended recipient, or an employee or agent responsible for
delivering this message to the intended recipient, you are hereby
notified that any dissemination, distribution, copying, or other use of
this message or its attachments is strictly prohibited. If you have
received this message in error, please notify the sender immediately by
replying to this message and please delete it from your computer. Any
views expressed in this message are those of the individual sender
unless otherwise stated.Company has taken enough precautions to prevent
the spread of viruses. However the company accepts no liability for any
damage caused by any virus transmitted by this email.
_____________________________________________________________________
