[arm-allstar] Software directions --was: Bug fix update!
Tim Sawyer
tisawyer at gmail.com
Wed May 24 21:47:36 EST 2017
I'm interested in what AllStar work you were doing and why you stopped.
Care to shed any light on that?
On Wed, May 24, 2017 at 6:08 PM, "Lowell via arm-allstar" <
arm-allstar at hamvoip.org> wrote:
> I too am waiting. I have stopped all my allstar work until it is.
>
>
> On Wed, May 24, 2017 at 5:36 PM, "Andrew Sylthe via arm-allstar" <
> arm-allstar at hamvoip.org> wrote:
>
> > I too am very curious to know when the source will be available.
> >
> > On May 24, 2017 6:50 PM, Pierre Martel via arm-allstar <
> > arm-allstar at hamvoip.org> wrote:
> >
> > > Interresting point. Are you planning on releasing the source later on?
> > >
> > >
> > >
> > >
> > > Le mer. 24 mai 2017 à 09:34, "David McGough via arm-allstar" <
> > > arm-allstar at hamvoip.org> a écrit :
> > >
> > > >
> > > > Hi Everyone,
> > > >
> > > > I wanted to make a few comments about software directions.
> > > >
> > > > Currently most of the code updates I'm making aren't being
> contributed
> > or
> > > > integrated back into the base AllStar repository. There are several
> > > > reasons for this.
> > > >
> > > > Much of the code and strategies I'm implementing are only targeted at
> > ARM
> > > > processors, such as the Cortex-A53 family found in the RPi3. Some of
> > > this
> > > > code won't even run on a x86 processor. I see the ARM architecture
> and
> > > > later derivatives being the future of AllStar--even in the scenario
> > where
> > > > you've got a hub server with dozens of users. To that end, I've been
> > > > carefully studying the "hot spots" (meaning high or critical CPU use
> > > > areas) and working hard on optimizing/parallelizing this code.
> > > >
> > > > Some have questioned the stability of an RPi3 when compared to a PC.
> > I've
> > > > found RPi boards, when properly setup (good power and adequate
> cooling)
> > > to
> > > > be just as reliable as any PC, even my favorite pcengines embedded
> > > boards!
> > > >
> > > >
> > > > 73, David KB4FXC
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > On Tue, 23 May 2017, "Brett Friermood via arm-allstar" wrote:
> > > >
> > > > > It's great seeing long standing bugs in asterisk/app_rpt/AllStar
> are
> > > > being
> > > > > fixed as time allows. Are these changes also being migrated to the
> > base
> > > > > repository or just being made within the HamVOIP code?
> > > > >
> > > > > Brett KQ9N
> > > > >
> > > >
> > > > _______________________________________________
> > > >
> > > > arm-allstar mailing list
> > > > arm-allstar at hamvoip.org
> > > > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> > > >
> > > > Visit the BBB and RPi2/3 web page - http://hamvoip.org
> > > >
> > > _______________________________________________
> > >
> > > arm-allstar mailing list
> > > arm-allstar at hamvoip.org
> > > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> > >
> > > Visit the BBB and RPi2/3 web page - http://hamvoip.org
> > _______________________________________________
> >
> > arm-allstar mailing list
> > arm-allstar at hamvoip.org
> > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> >
> > Visit the BBB and RPi2/3 web page - http://hamvoip.org
> _______________________________________________
>
> arm-allstar mailing list
> arm-allstar at hamvoip.org
> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>
> Visit the BBB and RPi2/3 web page - http://hamvoip.org
>
--
--
Tim
More information about the arm-allstar
mailing list