| Commit message (Collapse) | Author | Age |
|
|
|
|
|
| |
This is to keep the top-level directory clean, to make it clear what is
core and what is a port, and to allow the repository to grow with new ports
in a sustainable way.
|
|
|
|
| |
This is to have consistency across the whole repository.
|
| |
|
|
|
|
|
| |
Calls out to Zephyr's shell, submodule "net", command "iface", and shows
network interface information (if CONFIG_NET_SHELL is enabled).
|
|
|
|
|
|
|
|
| |
The original issue leading to crash on startup if no default network
interface was presented, was resolved some time ago.
Note that this enables generic networking subsystem, not networking
on Carbon.
|
|
|
|
| |
Was changed to "sa_family" for POSIX compatibility.
|
|
|
|
| |
As required for zephyr.stack_analyze().
|
|
|
|
|
|
| |
current_tid() returns current thread ID. stacks_analyze() calls
k_call_stacks_analyze() which, with CONFIG_INIT_STACKS enabled,
will print stack usage for some well-known threads in the system.
|
|
|
|
|
| |
$(TOP) is defined in py/mkenv.mk and should be used to refer to the top
level of this repository.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Accesses recv_q, accept_q directly in net_context.
|
|
|
|
|
| |
For some reason, with the latest Zephyr master, running just "make" led
to executing Zephyr's "qemu" target.
|
|
|
|
|
| |
There were several different spellings of MicroPython present in comments,
when there should be only one.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The code conventions suggest using header guards, but do not define how
those should look like and instead point to existing files. However, not
all existing files follow the same scheme, sometimes omitting header guards
altogether, sometimes using non-standard names, making it easy to
accidentally pick a "wrong" example.
This commit ensures that all header files of the MicroPython project (that
were not simply copied from somewhere else) follow the same pattern, that
was already present in the majority of files, especially in the py folder.
The rules are as follows.
Naming convention:
* start with the words MICROPY_INCLUDED
* contain the full path to the file
* replace special characters with _
In addition, there are no empty lines before #ifndef, between #ifndef and
one empty line before #endif. #endif is followed by a comment containing
the name of the guard macro.
py/grammar.h cannot use header guards by design, since it has to be
included multiple times in a single C file. Several other files also do not
need header guards as they are only used internally and guaranteed to be
included only once:
* MICROPY_MPHALPORT_H
* mpconfigboard.h
* mpconfigport.h
* mpthreadport.h
* pin_defs_*.h
* qstrdefs*.h
|
| |
|
|
|
|
|
| |
CONF_FILE can be overriden, e.g. for minimal build, and we don't construct
such overriden conf file like we do for prj_merged.conf.
|
|
|
|
|
|
| |
Got tired of running rm -rf manually. Make should clean, and should clean
fast. Also, fix always-running config-related commands (by having per-board
merged configs).
|
|
|
|
|
| |
In 1.8, Zephyr made a controversial change of dumping C99 stdint types
and switching to its own types.
|
| |
|
|
|
|
|
| |
Return value is mp_obj_t, so needs to be accessed using
MP_OBJ_SMALL_INT_VALUE().
|
| |
|
|
|
|
| |
Indeed, just "DEBUG" is too generic.
|
| |
|
|
|
|
|
|
|
|
|
| |
For consistent Pin/Signal class hierarchy. With it, Signal is a proper
(while still ducktyped) subclass of a Pin, and any (direct) usage of Pin
can be replace with Signal.
As stmhal's class is reused both as machine.Pin and legacy pyb.Pin,
high/low methods actually retained there.
|
| |
|
|
|
|
|
| |
If no network driver is enabled (e.g., it doesn't exist for a particular
board), it will be NULL.
|
|
|
|
| |
Instead, just peek a packet at the head of the queue and work with it.
|
|
|
|
|
| |
Here we wait for non-empty FIFO, and then directly access/drop its head
element.
|
| |
|
|
|
|
|
| |
This solves a case when socker_read() has blocked on fifo, and then peer
closed event arrives.
|
|
|
|
| |
Requires patch in review.
|
| |
|
|
|
|
|
| |
The most important info it returns are numbers of free buffers
in different pools (rx/tx packet headers, data fragments).
|
|
|
|
|
|
|
|
| |
There're a lot of changes and fixes in 1.8 regarding IP stack,
incompatible with previous Zephyr versions, so supporting them
doesn't make sense.
This is the last commit which should build with Zephyr 1.7.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Otherwise, if we already have a packet in progress, finish it first, before
check "peer closed" status.
|
| |
|
| |
|
| |
|
| |
|