Hello,
I'm writing a driver (amdisplay) supporting the LCD controller on the
am335x (Beaglebone Black). The LCD controller pins and the MMC1 pins
(used for interacting with the onboard eMMC flash chip) exist on the
same set of pads such that only the LCD controller or the eMMC may be
used at
On Tue, 4 Oct 2016 17:27:12 +0200
Mike Belopuhov wrote:
> On Tue, Oct 04, 2016 at 01:07 +0200, Vincent Gross wrote:
>> On Sat, 24 Sep 2016 10:58:10 +0200
>> Vincent Gross wrote:
>>
>> > Hi,
>> >
>> [snip]
>> >
>> > Aside from the mbuf issue, is this Ok
uvm_map_fill_vmmap lets callers specify an address after which they are
interested in entries. generally theyre interested in addresses after 0, but if
you start further along the address space the lookup has to traverse the
addresses looking for it.
this can be optimised by borrowing the
The sgi boot blocks use the PROM (ARCBios or ARCS) for its I/O routines.
When using a disk-based path, these routines are using the partition
table found in the ``volume header''.
In order to be able to use 16 partitions per disk, the OpenBSD port only
claims one volume header partition, #0, as
On Tue, Oct 04, 2016 at 07:46:52PM +0200, Rafael Zalamena wrote:
> This diff makes proc.c daemons to use less file descriptors on startup,
> this way we increase the number of child we can have considerably. This
> also improves the solution on a bug reported in bugs@
> "httpd errors out with 'too
This diff makes proc.c daemons to use less file descriptors on startup,
this way we increase the number of child we can have considerably. This
also improves the solution on a bug reported in bugs@
"httpd errors out with 'too many open files'".
To achieve that I delayed the socket distribution
On Tue, Oct 04, 2016 at 01:07 +0200, Vincent Gross wrote:
> On Sat, 24 Sep 2016 10:58:10 +0200
> Vincent Gross wrote:
>
> > Hi,
> >
> [snip]
> >
> > Aside from the mbuf issue, is this Ok ?
>
> I will go back on the mbuff stuff later.
>
> Diff rebased, ok anyone ?
>
>
FYI, sudo supports running the command in a new pty, which should
avoid the issue. Commands are always run in a new pty when logging
input or output, otherwise the use_pty flag needs to be set in
sudoers.
- todd
On 10/03/16 16:43, Martin Pieuchot wrote:
Diff below introduces a single write lock that will be used to serialize
access to ip_output().
This lock will be then split in multiple readers and writers to allow
multiple forwarding paths to run in parallel of each others but still
serialized with
On Tue 2016.10.04 at 15:29 +0200, Vadim Vygonets wrote:
> Quoth Okan Demirmen on Wed, Sep 28, 2016:
> > We currently print the x/y dimensions only for mouse based actions; we
> > don't for kbd, nor do we do anything with mouse/kbd window moves (such
> > as printing the x/y coordinates, etc). So
Quoth Okan Demirmen on Wed, Sep 28, 2016:
> We currently print the x/y dimensions only for mouse based actions; we
> don't for kbd, nor do we do anything with mouse/kbd window moves (such
> as printing the x/y coordinates, etc). So why have mouse-resize be
> different? Thus, the below crudely
On Tue, Oct 04, 2016, Otto Moerbeek wrote:
> On Tue, Oct 04, 2016 at 04:00:50AM -0700, Claus Assmann wrote:
> > This doesn't seem to resolve the problem that sa->rate is
> > not initialized, so a simple file like this still triggers
> Likely, this is better.
> RCS file:
On Tue, Oct 04, 2016 at 04:00:50AM -0700, Claus Assmann wrote:
> On Tue, Oct 04, 2016, Dmitrij D. Czarkoff wrote:
>
> [please do not Cc me]
>
> > I shouldn't have started on sending patches at 3AM. This one should do
> > what I intended it to do. Sorry for noise.
>
> > + else if (t
On Tue, Oct 04, 2016, Dmitrij D. Czarkoff wrote:
[please do not Cc me]
> I shouldn't have started on sending patches at 3AM. This one should do
> what I intended it to do. Sorry for noise.
> + else if (t == NULL && sa->minsz != sa->maxsz)
> + errx(1, "%s: parse
> Date: Tue, 4 Oct 2016 10:59:26 +0200
> From: Patrick Wildt
>
> Hi,
>
> continuing where we left off before the hackathon I would like to add
> a diff to the 64-bit bus_addr_t discussion. This diff does not
> increase the size of bus_addr_t. Instead it changes the argument
On Sat, Sep 24, 2016 at 07:05:54PM +0200, Mark Kettenis wrote:
> Another obvious mistake caught by clang.
>
> ok?
ok jsg@
>
>
> Index: dev/pv/hyperv.c
> ===
> RCS file: /cvs/src/sys/dev/pv/hyperv.c,v
> retrieving revision 1.16
>
Hi,
continuing where we left off before the hackathon I would like to add
a diff to the 64-bit bus_addr_t discussion. This diff does not
increase the size of bus_addr_t. Instead it changes the argument
of the function pointer stored in the bus tag from bus_addr_t to
uint64_t. This is an arm
Hi,
a colleague has been fiddling with ahci(4) wondering why the disk fails
on attach on his hardware. He came up with the following diff.
Considering this is quite an intrusive though small diff, I would like
to ask for tests on various hardware to make sure this does not break
any hardware we
18 matches
Mail list logo