search for: miros

Hi folks, Anyone know the whereabouts of libgtkembedmoz.so()(64bit) as it is needed by miro-1.0-1.el5.rf.x86_64 (rpmforge) I tried a whatprovides and have looked at epel as well as rpmforge - no luck. While I'm asking, I'm looking for an internet HD TV viewer - miro looked interesting - any other products you know of? TIA Rob -------------- next part -------------- A non-text attachment

...rebased on current drm-next - dropped staging/sm750fb changes - added kernel docs for DRM helpers v3: - move kerneldoc to fbdev, where functions are implemented - split kerneldoc for remove_conflicting_framebuffers() - propagate return value in remove_conflicting_pci_framebuffers() --- Micha? Miros?aw (13): fbdev: show fbdev number for debugging fbdev: allow apertures == NULL in remove_conflicting_framebuffers() fbdev: add kerneldoc do remove_conflicting_framebuffers() fbdev: add remove_conflicting_pci_framebuffers() drm/amdgpu: use simpler remove_conflicting_pci_framebuffers() dr...

...rebased on current drm-next - dropped staging/sm750fb changes - added kernel docs for DRM helpers v3: - move kerneldoc to fbdev, where functions are implemented - split kerneldoc for remove_conflicting_framebuffers() - propagate return value in remove_conflicting_pci_framebuffers() --- Micha? Miros?aw (13): fbdev: show fbdev number for debugging fbdev: allow apertures == NULL in remove_conflicting_framebuffers() fbdev: add kerneldoc do remove_conflicting_framebuffers() fbdev: add remove_conflicting_pci_framebuffers() drm/amdgpu: use simpler remove_conflicting_pci_framebuffers() dr...

Hi ALL: Suppose you have a population of N <- 5 observations, x <- c(43, 28, 7, 61, 39). From that you can draw a maximum of 10 samples without replacement of size n <- 3. (Command choose(N,n) yields 10). For instance the samples I seek are 43, 61, 7 39, 7, 28 ...etc How can I get R to do that for me, to get an exhaustive list of samples of size n drawn without replacement

Since i/we didn't receive any answer on secureshell at securityfocus.com I like to ask this question to you. What's your opinion on this topic? Thanks! Miro +-------------------------------+ +-------------------------------+ | Miro Dietiker | | MD Systems Miro Dietiker | +-------------------------------+ +-------------------------------+ -----Urspr?ngliche

...mba-3.0.11/samba-3.0.11/source/libsmb/smbencrypt.c:decode_pw_buffer(540) decode_pw_buffer: check that 'encrypt passwords = yes' MirOS is an OpenBSD derivate with a 64 bit "time_t" data type, so there are all kinds of weird problems lurking around... Thanks in advance, //mirabile -- > [...] Echtzeit hat weniger mit "Speed"[...] zu tun, sondern damit, da? der > richtige Proze? voraussagbar rechtzeitig se...

...series cleans up duplicated code for replacing firmware FB driver with proper DRI driver and adds handover support to Tegra driver. The last patch is here because it uses new semantics of remove_conflicting_framebuffers() from this series. This can be considered independently, though. --- Micha? Miros?aw (13): fbdev: show fbdev number for debugging fbdev: add remove_conflicting_pci_framebuffers() drm/amdgpu: use simpler remove_conflicting_pci_framebuffers() drm/bochs: use simpler remove_conflicting_pci_framebuffers() drm/cirrus: use simpler remove_conflicting_pci_framebuffers() drm/m...

...series cleans up duplicated code for replacing firmware FB driver with proper DRI driver and adds handover support to Tegra driver. The last patch is here because it uses new semantics of remove_conflicting_framebuffers() from this series. This can be considered independently, though. --- Micha? Miros?aw (13): fbdev: show fbdev number for debugging fbdev: add remove_conflicting_pci_framebuffers() drm/amdgpu: use simpler remove_conflicting_pci_framebuffers() drm/bochs: use simpler remove_conflicting_pci_framebuffers() drm/cirrus: use simpler remove_conflicting_pci_framebuffers() drm/m...

On Fri, Nov 24, 2017 at 06:53:31PM +0100, Micha? Miros?aw wrote: > Almost all drivers using remove_conflicting_framebuffers() wrap it with > the same code. Extract common part from PCI drivers into separate > remove_conflicting_pci_framebuffers(). > > Signed-off-by: Micha? Miros?aw <mirq-linux at rere.qmqm.pl> Since the only driv...

On Mon, Nov 27, 2017 at 08:52:19PM +0000, Sudip Mukherjee wrote: > On Mon, Nov 27, 2017 at 11:27:59AM +0100, Daniel Vetter wrote: > > On Fri, Nov 24, 2017 at 06:53:31PM +0100, Micha? Miros?aw wrote: > > > Almost all drivers using remove_conflicting_framebuffers() wrap it with > > > the same code. Extract common part from PCI drivers into separate > > > remove_conflicting_pci_framebuffers(). > > > > > > Signed-off-by: Micha? Miros?aw <m...

On Fri, Nov 24, 2017 at 06:53:31PM +0100, Micha? Miros?aw wrote: > Almost all drivers using remove_conflicting_framebuffers() wrap it with > the same code. Extract common part from PCI drivers into separate > remove_conflicting_pci_framebuffers(). > > Signed-off-by: Micha? Miros?aw <mirq-linux at rere.qmqm.pl> Since the only driv...

On Mon, Nov 27, 2017 at 08:52:19PM +0000, Sudip Mukherjee wrote: > On Mon, Nov 27, 2017 at 11:27:59AM +0100, Daniel Vetter wrote: > > On Fri, Nov 24, 2017 at 06:53:31PM +0100, Micha? Miros?aw wrote: > > > Almost all drivers using remove_conflicting_framebuffers() wrap it with > > > the same code. Extract common part from PCI drivers into separate > > > remove_conflicting_pci_framebuffers(). > > > > > > Signed-off-by: Micha? Miros?aw <m...

...n into it as COMBOOT, but that no longer > > works (this used to work for both ISOLINUX and PXELINUX, > > and the other two, although I rarely tested them). > > Now I?ve got a working method for PXELINUX, but that leaves > > the others still? > > Without rewriting the MirOS boot loader as a COM32 module, > reimplementing the COMBOOT system (which would likely have to be > mostly in C and be BIOS-only) or making the MirOS kernel act like > either an MBOOT kernel or a Linux kernel (for their boot protocols), > your closest generic alternative is chain.c32....

Not tested in any way. The original code for offload setting seems broken as it resets the features on every netback reconnect. This will set GSO_ROBUST at device creation time (earlier than connect time). RX checksum offload is forced on - so advertise as it is. Signed-off-by: Micha? Miros?aw <mirq-linux at rere.qmqm.pl> --- [I don't know Xen code enough to say this is correct. There is Xen netback driver coming in, that has similar changes to be made. Please match them up if you can.] drivers/net/xen-netfront.c | 57 +++++++++++++++++-------------------------- 1 files...

Not tested in any way. The original code for offload setting seems broken as it resets the features on every netback reconnect. This will set GSO_ROBUST at device creation time (earlier than connect time). RX checksum offload is forced on - so advertise as it is. Signed-off-by: Micha? Miros?aw <mirq-linux at rere.qmqm.pl> --- [I don't know Xen code enough to say this is correct. There is Xen netback driver coming in, that has similar changes to be made. Please match them up if you can.] drivers/net/xen-netfront.c | 57 +++++++++++++++++-------------------------- 1 files...

Not tested in any way. The original code for offload setting seems broken as it resets the features on every netback reconnect. This will set GSO_ROBUST at device creation time (earlier than connect time). RX checksum offload is forced on - so advertise as it is. Signed-off-by: Micha? Miros?aw <mirq-linux at rere.qmqm.pl> --- [I don't know Xen code enough to say this is correct. There is Xen netback driver coming in, that has similar changes to be made. Please match them up if you can.] drivers/net/xen-netfront.c | 57 +++++++++++++++++-------------------------- 1 files...

On 23 Sep 2015, at 18:10, Marcin Miros?aw <marcin at mejor.pl> wrote: > > With dovecot-2.2.19.rc1 still have this error. "doveadm backup" wants to delete and recreate a folder if there are some changes that can't be incrementally just added to it (mainly if IMAP UIDs would need to be inserted in the middle of...

...t) > > Normally I?d chain into it as COMBOOT, but that no longer > works (this used to work for both ISOLINUX and PXELINUX, > and the other two, although I rarely tested them). > Now I?ve got a working method for PXELINUX, but that leaves > the others still? Without rewriting the MirOS boot loader as a COM32 module, reimplementing the COMBOOT system (which would likely have to be mostly in C and be BIOS-only) or making the MirOS kernel act like either an MBOOT kernel or a Linux kernel (for their boot protocols), your closest generic alternative is chain.c32. chain.c32 is capable...

...KH wrote: > On Tue, Nov 28, 2017 at 11:22:17AM +0100, Daniel Vetter wrote: > > On Mon, Nov 27, 2017 at 08:52:19PM +0000, Sudip Mukherjee wrote: > > > On Mon, Nov 27, 2017 at 11:27:59AM +0100, Daniel Vetter wrote: > > > > On Fri, Nov 24, 2017 at 06:53:31PM +0100, Micha? Miros?aw wrote: > > > > > Almost all drivers using remove_conflicting_framebuffers() wrap it with > > > > > the same code. Extract common part from PCI drivers into separate > > > > > remove_conflicting_pci_framebuffers(). > > > > > > > &...

...KH wrote: > On Tue, Nov 28, 2017 at 11:22:17AM +0100, Daniel Vetter wrote: > > On Mon, Nov 27, 2017 at 08:52:19PM +0000, Sudip Mukherjee wrote: > > > On Mon, Nov 27, 2017 at 11:27:59AM +0100, Daniel Vetter wrote: > > > > On Fri, Nov 24, 2017 at 06:53:31PM +0100, Micha? Miros?aw wrote: > > > > > Almost all drivers using remove_conflicting_framebuffers() wrap it with > > > > > the same code. Extract common part from PCI drivers into separate > > > > > remove_conflicting_pci_framebuffers(). > > > > > > > &...