ibute and change the function
behavior to do nothing except return RTEMS_UNSATISFIED (in case someone somehow
still calls it), or better change it to call an RTEMS fatal function.
Peter
-
Peter Dufault
HD Associates, Inc. Software and System Engineering
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
se which you want at a later time.
>
> Kinsey
I've been moving a driver from legacy to bsd so I definitely need to easily
switch back and forth for the same BSP for testing.
I agree with Chris, but it's apparently a desirement, not a requirement, so it
shouldn't ho
the GCC commit needs to be updated.
> Maybe we should even wait for the GCC 13.3 release.
>
> I asked about a gcc 13.3 release and we should not wait. They intend to do a
> 14 release before returning to 13.3. We should plan to do 6.1 with a GCC 13
> branch hash and probably plan to swap that out with a 13.3 tarball when it's
> released.
>
> We are good at imposing more requirements. :)
>
>
Peter
-
Peter Dufault
HD Associates, Inc. Software and System Engineering
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
; RTEMS_BSP_IO_TRANSMISSION_COMPLETE? And following on you could have
>>> RTEMS_BSP_IO_NO_TRANSMISSION? The key point is "transmission" relates to the
>>> external data pin of the interface.
>>
>> The no-output option is used to just flush the device without transmitting a
>> new
>> character.
>
> Like what flush does?
>
>> For the flush, we could add something like this:
>>
>> Flushing the device should ensure that all characters handed over to the
>> device
>> for output are visible to external consumers. For example, the device output
>> FIFO and transmit shift registers should be empty.
>
> Lets just say transmitted. The devices we manage are embedded and so we
> receive
> and transmit data. Lets not introduce new or custom terms.
>
> Chris
> ___
> devel mailing list
> devel@rtems.org
> http://lists.rtems.org/mailman/listinfo/devel
Peter
-
Peter Dufault
HD Associates, Inc. Software and System Engineering
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
> On Apr 18, 2024, at 10:55 AM, Joel Sherrill wrote:
>
>
>
> On Thu, Apr 18, 2024 at 9:50 AM Peter Dufault wrote:
>
>
> > On Apr 18, 2024, at 10:34 AM, Kinsey Moore wrote:
> >
> > A patch for EEXIST here should be fine. It would be nice
> On Apr 18, 2024, at 10:55 AM, Joel Sherrill wrote:
>
>
>
> On Thu, Apr 18, 2024 at 9:50 AM Peter Dufault wrote:
>
>
> > On Apr 18, 2024, at 10:34 AM, Kinsey Moore wrote:
> >
> > A patch for EEXIST here should be fine. It would be nice
initialize();
assert(sc == RTEMS_SUCCESSFUL);
At least you get a panic message. I'll submit a patch.
Peter
-
Peter Dufault
HD Associates, Inc. Software and System Engineering
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
I just rebased to "6-freebsd-12". This change:
###
commit 62e0ca8283603573d42a0f15da044cd406a2f00a
Author: Kinsey Moore
Date: Tue Jan 23 13:25:45 2024 -0600
rtemsbsd/rtems: Check function return values
###
[dufault@gen6 rtems-libbsd]$ git diff 6514d561587fd1527fe6a26cb43e6b
> Feel free to submit a patch
>
Peter
-
Peter Dufault
HD Associates, Inc. Software and System Engineering
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
be other sections that do this.
>
> If this were wrapped in a conditional for the proper CPU core variants, it
> might resolve the issue. One would hope that if there were no e500 code,
> binutils and gdb wouldn't get confused.
>
> --joel
>
> On Wed, Mar 27, 2024 at
CTOR,
vector_base));
This line causes the ".o" to be "powerpc:titan" (if the above E500 lines are
removed):
ppc_mtivor(35, ppc_exc_vector_address(ASM_E500_PERFMON_VECTOR, vector_base));
I "#ifdef'd" them out to get it to "work" but unless someon
This is for 6-freebsd-12. How is that specified? I don't see [PATCH
libbsd-6-freebsd-12] etc.
> On Feb 1, 2024, at 6:00 AM, dufa...@hda.com wrote:
>
> From: Peter Dufault
>
> - safe_pause_us() and safe_pause_ms() depend on the clock tick. Use DELAY().
> ---
From: Peter Dufault
- safe_pause_us() and safe_pause_ms() depend on the clock tick. Use DELAY().
---
freebsd/sys/dev/e1000/e1000_osdep.h | 12
1 file changed, 12 insertions(+)
diff --git a/freebsd/sys/dev/e1000/e1000_osdep.h
b/freebsd/sys/dev/e1000/e1000_osdep.h
index 70db294
From: Peter Dufault
- Fix detection of timeout in rtems_shell_term_wait_for().
- Use the "termios" VTIME inter-character timeout.
The previous version depends on the BSP clock tick and can be long.
- Add debugging regarding terminal size sequences.
Updates #4763
---
cpukit/lib
> On Jan 23, 2024, at 7:09 PM, Chris Johns wrote:
>
> On 23/1/2024 9:00 pm, Peter Dufault wrote:
>>> On Jan 22, 2024, at 1:51 PM, Peter Dufault wrote:
>>>> On Jan 22, 2024, at 12:16 PM, Gedare Bloom wrote:
>>>>
>>>> I have a coup
> On Jan 22, 2024, at 1:51 PM, Peter Dufault wrote:
>
>
>
>> On Jan 22, 2024, at 12:16 PM, Gedare Bloom wrote:
>>
>> I have a couple minor notes below. More important, does this change
>> require updating documentation?
>
> I'd have
t;
> I know we have a somewhat aging shell-specific guide:
> https://docs.rtems.org/branches/master/shell/index.html
>
>
> On Fri, Jan 19, 2024 at 5:19 AM wrote:
>>
>> From: Peter Dufault
>>
>> - Fix detection of timeout in rtems_shell_term_wait_for(
From: Peter Dufault
- Fix detection of timeout in rtems_shell_term_wait_for().
- Switch to using "termios" VTIME inter-character timeout.
The previous implementation is dependent on the BSP clock tick value.
Updates #4763
---
cpukit/libmisc/shell/she
From: Peter Dufault
This is my first submission of a patch using format-patch and
send-email from my Linux system. Let me know if anything is wrong.
Peter Dufault (1):
libmisc/shell: Fix timeout in getting terminal size
cpukit/libmisc/shell/shell.c | 101
d to open a bug first?
Only downside is VTIME needs to be multiples of .1 seconds, so it will be .1 or
.2.
The VTIME and VMIN is a good interface *except* that the VTIME>0 VMIN>0 case
initial timeout is infinity. I don't like that, though I suppose an alarm and
EINTR would let me do
> On Jan 5, 2024, at 1:36 PM, Peter Dufault wrote:
>
> I "#if 0"d out the call to "rtems_shell_term_row_column_swapped()" that
> checks for a broken "tmux" terminal. That is what sends "\033[>0q" to the
> console. I no long
t calls every command.
The escape sequence does work on gnome-terminal, so I'm not sure what causes
the delay. I can investigate that, but question if this
should be done in the shell.
[dufault@gen6 rtems]$ echo -e "\e[18t"
^[[8;42;111t
[dufault@gen6 rtems]$
Peter
--
nal size as env variables
Closes #4763
Which has this:
fputs("\033[>0q", stdout);
I backed it out for now. Anyone else seeing this?
Peter
-
Peter Dufault
HD Associates, Inc. Software and System Engineering
___
d
ent something like that.
I have thought about this. It's more hand-coding for the control loops, but
it's traditional coding. Not everyone thinks the eTPU/PowerPC architecture is
as well-designed as I do - "Way too complicated!" is the feedback I get.
Peter
-
IP" and the integration is up to the licensor. That said, ARM works
well.
> On Sep 14, 2023, at 15:22 , o...@c-mauderer.de wrote:
>
> Hello Peter,
>
> Am 13.09.23 um 19:22 schrieb Peter Dufault:
>>> On Jul 25, 2023, at 10:14 , Joel Sherrill wrote:
>>>
>
he old Motorola PowerPC's architecture targeted at engine control,
I will miss how the ADC DMA chain works together with the eTPU and also
schedules the output so cleanly do background motor control, and other timing
intensive applications, so that the main CPU is free to e.g. run R
ity
> order:
>
> 1. Real-time Impacts + Maintainability Loss
> 2. Transparency Loss + Modularity Loss + Code/RAM Size Increase
> 3. Performance Loss
>
> I wrote each goal now as a "minimize" objective. I think it is not
> possible to establish strict priorities on
st be providing this as a
fall-back address. It happens infrequently.
Does the libbsd DHCP client have fall back to provide a private address, e.g.
"169.254.208.184"?
I did some searching in "libbsd" but didn't find it.
Peter
-
Peter Dufault
HD Associat
n"
"clientid\n"
"nodhcp6\n"
"ipv4only\n"
"timeout 0\n"
"interface ffec0\n"
"option bootfile_name\n"
"option root_path\n"
"\n";
Peter
-
Peter Dufault
H
t; Chris
I see online that DHCP option 129 has three definitions: "PXE - undefined
(vendor specific)", "Kernel options Variable length string", and "Call Server
IP address".
Above does "option rtems_cmdline" and "define 129 string rtems_cmdline" s
;option" variable for use in
"/usr/local/libexec/dhcpcd-run-hooks".
which would be an argv of {"dhcpcd", "--option", "17", NULL }.
Or is best practice to do something with "rtems-bsd-rc-conf-net.c"?
Peter
-
his realistic? I looked at the list of board support packages output by
"./rtems-bsps" in RTEMS-6 and there are many old ones (M68K, old VME boards)
that I assume use the legacy stack and aren't likely to be updated to use LWIP
or "libbsd" and where the old stack works and h
> On Jul 6, 2021, at 06:42 , Chris Johns wrote:
>
>> On 3 Jul 2021, at 5:14 am, Peter Dufault wrote:
>>
>> I updated my libbsd today and an application is failing to build because it
>> can't find the include file "rtems/bsd/test/network-config.h&qu
I want to build the i.MX RT BSP with a custom DTS file. It's easy to build an
application using ones own "dts.o" file, but I want to build all the BSP tests
with my dts.o. For now I just change the one in the tree but I don't want to
do that. I don't want a BSP variant, either, since it's a c
I updated my libbsd today and an application is failing to build because it
can't find the include file "rtems/bsd/test/network-config.h". It was added
yesterday to "rtemsbsd/include/bsp/nexus-devices.h". "nexus-devices.h" the
only file outside of the testsuite directory that includes "network
> On Jun 23, 2021, at 01:17 , Sebastian Huber
> wrote:
>
>
> On 21/06/2021 15:31, dufa...@hda.com wrote:
>>> On Jun 21, 2021, at 08:52 , Sebastian
>>> Huber wrote:
>>>
>>> What happens when you reduce the memory space for the mbufs to 4MiB? What
>>> is the "RTEMS work space"?
>> By "RTEMS
I'll put it in at compile time but looking at the code that won't make a
difference.
Peter
-
Peter Dufault
HD Associates, Inc. Software and System Engineering
This email is delivered through the public internet using protocols subject to
interception and tamperin
committed to run in 8MB RAM and 16MB FLASH on the "imxrt" BSP.
I've got 7.8MB of RTEMS work space out of my 8MB of RAM and can't get a network
application to start up after trying to reduce the configuration.
Peter
-
Peter Dufault
HD Associates, Inc. Softwa
articularly want to redo my HyperRAM
initialization to avoid using stack since I'm calling some NXP functions. I'd
like a small amount of stack available in the context of bsp_start_hook_0() to
set up the external RAM.
- What's going on in the shared ARM _start with bsp_start
bootstrap properly but evidently not.
>
> Do you need to use multiple prefixes to support multiple build sets? I
> wanted to try the minimal one first before installing.
>
I removed the installed "imxrt1052" BSP and then it worked.
Peter
-
Peter Dufault
HD A
the build woiuld bootstrap properly but evidently not.
Do you need to use multiple prefixes to support multiple build sets? I wanted
to try the minimal one first before installing.
Peter
-
Peter Dufault
HD Associates, Inc. Software and System Engineering
This email is deli
rd one.
Peter
-----
Peter Dufault
HD Associates, Inc. Software and System Engineering
This email is delivered through the public internet using protocols subject to
interception and tampering.
signature.asc
Description: Message signe
> On Jun 11, 2021, at 08:07 , Christian Mauderer wrote:
>
> Hello Peter,
>
> On 11/06/2021 13:23, Peter Dufault wrote:
>> I tried to build the "minimal" buildset for the IMXRT BSP and I get
>> undefined INET6 references - _bsd_inet6_pfil_hook, _bsd_ip6sta
The libbsd is a recent 6-freebsd=12
is "minimal" built regularly? Any hints?
Peter
-
Peter Dufault
HD Associates, Inc. Software and System Engineering
This email is delivered through the public internet using protocols subject to
interception and tampering.
sign
to be in on-chip RAM and we can't
access anything outside of on-chip RAM until after we finish setting HyperRAM
up in "bsp_start_hook_0()".
The code for the "imxrt" "_start" assigns something to the stack pointer that
isn't mapped yet if we haven't se
{
> rbar = (uintptr_t) begin | region | ARMV7M_MPU_RBAR_VALID;
> rasr |= _ARMV7M_MPU_Get_region_size(size);
> } else {
> --
> 2.26.2
>
> ___
> devel mailing list
> devel@rtems.org
> http://lists.rtems.org/mailman/listinfo/devel
override what to use as "cmake" in RSB to specify "cmake3"?
> >>
> >>> On Apr 30, 2021, at 04:41 , Peter Dufault wrote:
> >>>
> >>> I verified my environment is squeaky-clean with a simple path and no
> >>> environment va
mespec(
> &queue_context,
> - abstime
> + abstime,
> + true
> );
> _Mutex_Acquire_slow( &mutex->Mutex, owner, executing, level,
> &queue_context );
>
> diff --git a/cpukit/score/src/threadqtimeout.c
> b/cpukit/score/sr
> On Apr 30, 2021, at 05:03 , dufa...@hda.com wrote:
>
> Can I override what to use as "cmake" in RSB to specify "cmake3"?
>
>> On Apr 30, 2021, at 04:41 , Peter Dufault wrote:
>>
>> I verified my environment is squeaky-clean with a sim
I lied. I had /usr/local/bin in my path to pick up "cmake3" instead of the
system "cmake". I thought I repeated the test with PATH set to just /usr/bin
and /usr/sbin, but I hadn't.
Can I override what to use as "cmake" in RSB to specify "cmake3"?
ffect RTEMS or "make".
Here's what happened. I'm including the patch because I just noticed the one
file that is patched is the one that doesn't compile the first time.
RTEMS Tools Project - Source Builder Error Report
Build: error: building soem-powerpc-rtems6-1
From: Peter Dufault
With these two changes the "powerpc/shared/console" code supports a
configurable baud rate.
Peter Dufault (2):
powerpc/shared/console: Make console baud rate configurable.
powerpc/shared/console: "termios" first open sets console baud to 9600
From: Peter Dufault
The "powerpc/shared/console" code has the start-up console value fixed
at 9600 baud. This changes the hard-wired constant "9600" in the code
to the configuration setting "BSP_CONSOLE_BAUD" and adds configuration
support in both the "waf&qu
From: Peter Dufault
When the PowerPC shared console baud rate starts at anything other than
9600 the termios code will set it to 9600 at the first open.
---
bsps/powerpc/shared/console/uart.c | 4
1 file changed, 4 insertions(+)
diff --git a/bsps/powerpc/shared/console/uart.c
b/bsps
I forgot to specify V2. I'll try again, sorry for the noise.
> On Apr 27, 2021, at 13:40 , wrote:
>
> From: Peter Dufault
>
> With these two changes the "powerpc/shared/console" code supports a
> configurable baud rate.
>
> - Remove hard-wired start-u
From: Peter Dufault
When the PowerPC shared console baud rate starts at anything other than
9600 the termios code will set it to 9600 at the first open.
---
bsps/powerpc/shared/console/uart.c | 4
1 file changed, 4 insertions(+)
diff --git a/bsps/powerpc/shared/console/uart.c
b/bsps
From: Peter Dufault
The "powerpc/shared/console" code has the start-up console value fixed
at 9600 baud. This changes the hard-wired constant "9600" in the code
to the configuration setting "BSP_CONSOLE_BAUD" and adds configuration
support in both the "waf&qu
From: Peter Dufault
With these two changes the "powerpc/shared/console" code supports a
configurable baud rate.
- Remove hard-wired start-up baud of 9600.
- Fix "termios" first-open that resets baud rate to 9600.
Peter Dufault (2):
powerpc/shared/console: Make console ba
PCI
multi-port serial driver for an eight port PMC serial port card. Some of the
files will need to be shuffled around.
Peter
-
Peter Dufault
HD Associates, Inc. Software and System Engineering
This email is delivered through the public internet
eduler". So
"ineligible" is good. That's based on the mailings and not the code.
Peter
-
Peter Dufault
HD Associates, Inc. Software and System Engineering
This email is delivered through the public internet using protocols subject to
interception an
act it was digitally signed that looked
odd.
At any rate, this patch should at least be received properly.
Peter
-
Peter Dufault
HD Associates, Inc. Software and System Engineering
This email is delivered through the public internet using protocols subject to
interception and ta
From: Peter Dufault
The "powerpc/shared/console" code has the start-up console value fixed
at 9600 baud. This changes the hard-wired constant "9600" in the code
to the configuration setting "BSP_CONSOLE_BAUD" and adds configuration
support in both the "waf&qu
From: Peter Dufault
The "powerpc/shared/console" code has the start-up console value fixed
at 9600 baud. This changes the hard-wired constant "9600" in the code
to the configuration setting "BSP_CONSOLE_BAUD" and adds configuration
support in both the "waf&qu
From: Peter Dufault
When the PowerPC shared console baud rate starts at anything other than
9600 the termios code will set it to 9600 at the first open.
---
bsps/powerpc/shared/console/uart.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/bsps/powerpc/shared/console/uart.c
b/bsps
ottom of BSP_uart_termios_set().
Is this a different patch (since it is a separate issue) or a [2/2] patch to
the "Make console baud rate configurable" patch (since the issue didn't show up
as the start-up baud rate was fixed at 9600 anyway)?
Peter
-
Peter Dufault
HD
> On Apr 9, 2021, at 11:53 , Peter Dufault wrote:
>
> The "powerpc/shared/console" code has the start-up console value fixed
> at 9600 baud. This changes the hard-wired constant "9600" in the code
> to the configuration setting "BSP_CONSOLE_BAUD"
The "powerpc/shared/console" code has the start-up console value fixed
at 9600 baud. This changes the hard-wired constant "9600" in the code
to the configuration setting "BSP_CONSOLE_BAUD" and adds configuration
support in both the "waf" and the legacy configuration systems.
Note that the VME BSP
et of the BSPs
>> in "ARCH".
>
> This is the wrong level for BSP-specific options. You have to look for:
>
> spec/build/bsps/ARCH/FAMILY/grp.yml
This won't work, "powerpc/shared/console" is shared across powerpc FAMILYs:
[dufault@gen6 powerpc]$ grep
the
"powerpc/{beatnik/haleakala,motorola_powerpc,mvme3100,mvme5500}/bsp*.yml}"
files to add the build-dependency on "uid: ../../optconsolebaud" can I put it
in the "spec/build/bsps/powerpc/grp.yml" file?
Peter
-
Peter Dufault
HD Associates, Inc. Softwa
5xxevb/configure.ac" still uses "BSP_DEFAULT_BAUD_RATE"
while the "waf" build system changed the code and configuration name to the
standardized "BSP_CONSOLE_BAUD". I didn't fix it since it's not associated
with the powerpc/shared changes, but it is bit
cleaned up.
3. Is it correct to update the "configure.ac" files when new options are added
or are those now considered defunct?
Peter
-
Peter Dufault
HD Associates, Inc. Software and System Engineering
This email is delivered through the public interne
I re-read Joel's mail and I agree, the priority should be left ridiculously low
(as it is now) or maybe set in the middle (but why bother?).
I was thinking about matching classic RTEMS behavior. I don't think it matters
in POSIX.
> On Feb 23, 2021, at 17:12 , Peter Dufault wrote
rio)?
> > > There is no option to configure the priority of the POSIX initialization
> > > thread, so the default priority of 2 is used, see
> > > _POSIX_Threads_Default_attributes.
> > >
> > > --
> > > embedded brains GmbH
> > > Herr Sebastian HUBER
> > > Dornier
> On Feb 18, 2021, at 12:49 , Gedare Bloom wrote:
>
> willing to buy: style formatter.
I'll buy one too.
Peter
-----
Peter Dufault
HD Associates, Inc. Software and System Engineering
This email is delivered through the public internet using protoc
nicode discussion:
testsuites/fstests/fsdosfsname01/create_files.cs
It's full of Unicode.
Peter
-
Peter Dufault
HD Associates, Inc. Software and System Engineering
This email is delivered through the public internet using protocols subject to
interception
use the English name for our organization as well.
>
> The answer might take some time, though.
>
>
>
> Best regards,
>
>
>
> Jan
>
>
>
> From: Joel Sherrill
> Sent: Monday, February 15, 2021 9:41 PM
> To: Peter Dufault
> Cc: Sommer,
he list now before we push these changes.
>>
>
> There is an u-Umlaut in it. That is probably it. As it is part of the name,
> it's hard to get rid of.
> I could probably use the English name (German Aerospace Center) which has no
> special characters.
> Woul
ucks.
>
>
> I don't see not running them as a good option. Beyond adding a new state to
> reflect this oddity, any suggestions?
>
> --joel
> ___
> devel mailing list
> devel@rtems.org
> http://lists.rtems.org/mailman/listinfo/devel
> ___
> On Jan 29, 2021, at 13:59 , Gedare Bloom wrote:
>
>
>
> On Fri, Jan 29, 2021 at 11:38 AM Joel Sherrill
> wrote:
>
>
> On Fri, Jan 29, 2021, 12:28 PM Sebastian Huber
> wrote:
> On 29/01/2021 18:33, Peter Dufault wrote:
>
> >>> Do not
hat
are the same enum.
I avoid using #define. In most situations you can't print them in a debugger
and they imply restricted usage.
Is this an appropriate warning? Does it always mean that the enum should be
replaced with a #define?
If it doesn't always apply then the style should
x27;t a big deal, and "Get_*_by_id" can be used going forward to
imply the ID needs validation as opposed to getting it from a valid
Thread_Control.
I have to research the RTEMS naming convention. I know it must be well-defined
and not Random_case.
Peter
-
cide not to.
> "Get" was already used. This is a "Get" when we know the identifier is valid.
> Do you have a better verb?
>
Valid_ID_Get? Or is that getting too wordy?
I like "_ValID_" (i.e. use "ValID" in interface names for validated IDs) but
t
Vertretungsberechtigte Geschäftsführer: Peter Rasmussen, Thomas Dörfler
> Unsere Datenschutzerklärung finden Sie hier:
> https://embedded-brains.de/datenschutzerklaerung/
>
> _______
> devel mailing list
> devel@rtems.org
> http://lists.rte
Actually, replying to myself:
I bet the context-switching code is broken for platforms that use the SPE via a
Freescale library. That's something I'll need to look at.
> On Jan 22, 2021, at 14:26 , Peter Dufault wrote:
>
> Signed PGP part
> The PowerPC Signal Processi
dy know anything the quality of the "powerpc-spe" support in
Clang/LLVM?
This is must an exploratory question. I don't have a plan to work on this soon.
Peter
-
Peter Dufault
HD Associates, Inc. Software and System Engineering
This email is delivered thro
st
> devel@rtems.org
> http://lists.rtems.org/mailman/listinfo/devel
> ___
> devel mailing list
> devel@rtems.org
> http://lists.rtems.org/mailman/listinfo/devel
Peter
-
Peter Dufault
HD Associates, Inc. Software
anks Sebastian.
>
It had me confused at first when I started working with ARM.
Peter
-
Peter Dufault
HD Associates, Inc. Software and System Engineering
This email is delivered through the public internet using protocols subject to
interception and tampering.
signature.asc
I'm building "Simple Open EtherCAT Master" with rtems-6. I built it earlier
with rtems-5. I get the following error when I try to build it:
[dufault@build scripts]$
/home/dufault/development/rtems/rtems-source-builder/source-builder/sb-set-builder
\
--log=log_arm_soem \
de overhead is an issue. If
you're testing I2C from the shell I'm not sure when it's important to have only
e.g. i2cget but not i2cset.
Peter
-
Peter Dufault
HD Associates, Inc. Software and System Engineering
This email is delivered through the public
richt München
>> Registernummer: HRB 157899
>> Vertretungsberechtigte Geschäftsführer: Peter Rasmussen, Thomas Dörfler
>> Unsere Datenschutzerklärung finden Sie hier:
>> https://embedded-brains.de/datenschutzerklaerung/
>>
>> ___
>&g
n"
>> - "\tmounts the file system of each partition of the disk\n"
>> - "\n"
>> - "fdisk DISK_NAME unmount\n"
>> - "\tunmounts the file system of each partition of the disk\n"
>> + "\tdeletes the logical disks associated with the partitions\n"
>>
t; Good, I added a ticket for this:
>
> https://devel.rtems.org/ticket/4134#ticket
>
> It is not on my high priority list.
>
> ___
> devel mailing list
> devel@rtems.org
> http://lis
ist
> devel@rtems.org
> http://lists.rtems.org/mailman/listinfo/devel
The footprint is larger. I forget exactly which board I was evaluating but I
couldn't always use the "libbsd" stack and made it conditional.
I didn't spend much time trying to reduce the foot
wc -l
> 710
>
> That doesn't count timer_service_routine, the one for signals, etc.
>
> I'm not opposed and now is the time if there is consensus. I have reached the
> point where I acknowledge the long history and mostly am concerned about how
> changes impact user code
at:
- Status codes are an integral type;
- Status codes of 0 always mean success.
Trying to pretend you need to compare a return to a special "success" #define
that is 0 is pointless and error prone now-a-days IMHO.
If I really wanted a return code that was special I'd do something like:
ty
_______
> devel mailing list
> devel@rtems.org
> http://lists.rtems.org/mailman/listinfo/devel
> ___
> devel mailing list
> devel@rtems.org
> http://lists.rtems.org/mailman/listinfo/devel
Peter
-
Pete
with an RTEMS configuration with no diffs regardless
of how you reformatted the input.
I know this would use the same tool that is being tested to create the input
test files, but I think in this case it's OK due to how invasively "uncrustify"
can be configured to reformat the
sh Rai wrote:
>>
>>
>>
>> On Fri, Jul 3, 2020 at 1:32 AM Peter Dufault wrote:
>> I finally have gotten to reviewing Utkarsh's work in GSOC. One item that I
>> don't like is that there is a linked list management of the threads that
>> have
My thought is that it matches what is needed and is expected to be optimized.
> On Jul 3, 2020, at 24:37 , Utkarsh Rai wrote:
>
>
>
> On Fri, Jul 3, 2020 at 1:32 AM Peter Dufault wrote:
> I finally have gotten to reviewing Utkarsh's work in GSOC. One item that I
>
reads need access to which thread.
However, it won't scale infinitely. Linked lists won't scale infinitely in
real-time either.
Peter
-
Peter Dufault
HD Associates, Inc. Software and System Engineering
This email is delivered through the public internet using protocol
1 - 100 of 243 matches
Mail list logo
